-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat(action): introduce ecs task definition deploy action #17
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for this, @IamAbbey! This is looking great already. I left a couple of comments and a few questions. If it's easier for you to discuss the questions in particular, we can also just call about this on Monday.
if allow_empty and not active_task_definitions: | ||
return "" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you explain your reasoning for allow_empty
? It seems you are setting it to true in the action. Naively, I would think that not finding exactly one active task definition with the tag should always be an exception.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The first time a deployment is made
The script will fail because at that time there wont be a task definition with the tag created_by: Github Actions Deployment
So the script needs to configurably allow for empty result, by default it's False
We have merged https://github.com/moneymeets/moneymeets-pulumi/pull/545 and moneymeets/action-ecs-deploy#1 I think the pull request here can be closed, @IamAbbey. |
@IamAbbey, do you still need the branch? If not, please also delete. Thanks! |
This action will be used in our deploy workflow