Skip to content
This repository has been archived by the owner on Sep 13, 2024. It is now read-only.

Add volume to rpm/deb package #478

Merged
merged 4 commits into from
Feb 21, 2022
Merged

Conversation

Realmonia
Copy link
Contributor

Summary

This PR cherry-picks the previous volume plugin updates commits, and remove the curl line which breaks during release init build, also updates the readme for customized rpm build

Implementation details

See previous PRs #450 and #462

Testing

New tests cover the changes: N/A

Tests done for pr #450 and #462 :

  1. Build ecs-init locally
  2. Upload ecs-init to S3
  3. Update install script to use above ecs-init
  4. Use updated install script to run MACIS ECS anywhere tests

Tests done for fixing the release build failure: test build in shadow stage pipeline

Description for the changelog

Licensing

This contribution is under the terms of the Apache 2.0 License:

@@ -0,0 +1,23 @@
# Copyright 2020 Amazon.com, Inc. or its affiliates. All Rights Reserved.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Q. should it be updated to Copyright 2022 Amazon.com, Inc for

  • packaging/generic-rpm/amazon-ecs-volume-plugin.service
  • packaging/generic-rpm/amazon-ecs-volume-plugin.socket
  • packaging/generic-deb/debian/amazon-ecs-volume-plugin.service
  • packaging/generic-deb/debian/amazon-ecs-volume-plugin.socket ?
    Thanks.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Q. should we reuse existing amazon-ecs-volume-plugin.service and amazon-ecs-volume-plugin.socket in the amazon-linux-ami folder instead of creating new files? Thanks.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

should we reuse existing amazon-ecs-volume-plugin.service and amazon-ecs-volume-plugin.socket in the amazon-linux-ami folder instead of creating new files?

I see that all the packaging folders have their own ecs.service file as well, I'm not sure if the reason behind might this was to make the packaging folders to be self contained but ya I do not have a preference in this.

Copy link
Contributor Author

@Realmonia Realmonia Feb 17, 2022

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated all touched files to 2022. For the existing files my thought is same as Mythri's idea to have each packaging folders self contained and could be separated easily if we want to have different build root. And in case we have different setups for different platforms we gain more flexibilities on it. Users making their own packages could also easily understand the hierarchy and only modify stuff under the platform they concern.

@Realmonia Realmonia merged commit c060ff3 into aws:dev Feb 21, 2022
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants