Skip to content
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: allow to force latest deploy using latest available task definition #240

Closed

Conversation

syphernl
Copy link

What was changed

  • Added argument --use-latest-task-def-forced to be used in conjunction with --use-latest-task-def
  • When provided, it will use the latest available Task Definition and force-deploy that rather than using the currently used Task Definition.

Background info

Initially I had it use the latest Task Definition automatically when --use-latest-task-def was being used, but decided on adding an argument to retain existing behavior.

References

Closes #239

@syphernl
Copy link
Author

syphernl commented Feb 2, 2023

This project seems unmaintained. Closing stale MR.

@syphernl syphernl closed this Feb 2, 2023
@forevermatt
Copy link
Contributor

@syphernl I am sorry that we did not manage to respond to your pull request. Along the lines of what you suspected, this project is in maintenance mode, so only bug-fix PRs are considered at this point.

Thank you for helping us clean up stale PRs, and I apologize again that your work did not make it into the codebase. Thank you for the time you spent in an effort to improve this tool for all of us.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

Force new deployment using latest task definition
2 participants