feat: Allow Option to add CPU and MEMORY values #399
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
jaishankar101
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Issue #, if available:
When tasks are managed from an external infrastructure repository, it’s often necessary to specify compute resource requirements (CPU and memory) specific to each service. Currently, these values are not easily configurable from within the service repository, making it difficult to customize or update resource requirements as their service needs evolve.
Description of changes:
This PR adds support for custom CPU and memory allocation by introducing new input fields to the GitHub Action. These fields allow users to specify cpu and memory values when updating the ECS task definition. With this change, service repositories can independently manage their own resource requirements without relying on changes in the infrastructure repo, improving autonomy, flexibility, and DevOps best practices.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.