feat: Allow setting codedeploy-config-name as input#506
feat: Allow setting codedeploy-config-name as input#506c-ameron wants to merge 3 commits intoaws-actions:masterfrom
Conversation
There was a problem hiding this comment.
👍
I like it, i like to have fast, normal, slow deployment roll options. depending on environment, time of day, whether manual or automated, risk level of the change, etc. This allows us to do this in the ci/cd flow instead of terraforming a change to the deployment object first.
|
@iamhopaul123 @KollaAdithya are you able to have a look at this PR? Thanks! |
3f89b76 to
63147fe
Compare
|
Any updates on merging this one? Would love to get away from using a fork as a workaround :) |
|
Hi @c-ameron, Thank you for your Patience. We appreciate your contribution to the repository and will be working to review the changes in the Pull Request. We will reach-out if with any questions or suggestions during the review. In the meantime please ensure that below steps, if not already completed, are taken care of in your Pull Request:
|
|
Hi, Thank you for your contribution in this PR. We have recently merged a PR that covers these changes. PR #540. The changes will be released as part of next release. Closing this PR, please feel free to re-open or create additional PRs for other feature requests or support needed. Thank you! |
Issue #479 , if available:
Description of changes:
This allows the setting of the config name of the deployment in Code Deploy via the
codedeploy-config-nameinput variable.By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.