You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 13, 2024. It is now read-only.
We would like comments on: How the proposed changes will affect your use case.
Problem Statement
Presently we have separate repositories for the Amazon ECS Agent and for ECS Init. The separation requires us to maintain build synchronization mechanisms to require the ECS Agent Image as a prerequisite to the RPM/DEB targets included in ECS Init’s Makefile. This separation forces a more complicated build process which inhibits us from taking full advantage of the software that builds rpm/deb packages (for example see: https://fedoraproject.org/wiki/Koji).
Standalone Repository Deprecation - ECS Init
To streamline and unify our build process, we plan on merging ECS Init and its related components into the ECS Agent repository. We will be augmenting the ECS Agent Makefile with all existing ECS Init targets, (as well as adding a few more targets to facilitate neater end-to-end builds.) The updated process will allow us to create our rpm/deb build targets without dependencies on external/separate ECS Agent image builds. It will simplify the overall code and will make testing ECS Init with ECS Agent more manageable.
The merge of ECS Init into ECS Agent will include the full commit history. In the near term, we will still be actively updating the ECS Init repository as well as updating the ECS Init code inside the ECS Agent repository.
We are not proposing that ECS Init itself will be deprecated, rather that the standalone repository which encapsulates the ECS Init functionality will be deprecated and ECS Init and all its related components will be integrated into the ECS Agent repository.
The text was updated successfully, but these errors were encountered:
The ECS team is planning on merging ECS Init and its related components into https://github.com/aws/amazon-ecs-agent and deprecating the standalone https://github.com/aws/amazon-ecs-init repository.
We would like comments on:
How the proposed changes will affect your use case.
Problem Statement
Presently we have separate repositories for the Amazon ECS Agent and for ECS Init. The separation requires us to maintain build synchronization mechanisms to require the ECS Agent Image as a prerequisite to the RPM/DEB targets included in ECS Init’s Makefile. This separation forces a more complicated build process which inhibits us from taking full advantage of the software that builds rpm/deb packages (for example see: https://fedoraproject.org/wiki/Koji).
Standalone Repository Deprecation - ECS Init
To streamline and unify our build process, we plan on merging ECS Init and its related components into the ECS Agent repository. We will be augmenting the ECS Agent Makefile with all existing ECS Init targets, (as well as adding a few more targets to facilitate neater end-to-end builds.) The updated process will allow us to create our rpm/deb build targets without dependencies on external/separate ECS Agent image builds. It will simplify the overall code and will make testing ECS Init with ECS Agent more manageable.
The merge of ECS Init into ECS Agent will include the full commit history. In the near term, we will still be actively updating the ECS Init repository as well as updating the ECS Init code inside the ECS Agent repository.
We are not proposing that ECS Init itself will be deprecated, rather that the standalone repository which encapsulates the ECS Init functionality will be deprecated and ECS Init and all its related components will be integrated into the ECS Agent repository.
The text was updated successfully, but these errors were encountered: