Releases: DNXLabs/terraform-aws-ecs
6.9.0
What’s Changed
Adding tags variable @mvsnogueira-dnx (#56)
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.Types of changes
What types of changes does your code introduce to <repo_name>?
Put an x in the boxes that apply
- Bugfix (non-breaking change which fixes an issue)
- New feature (non-breaking change which adds functionality)
- Breaking change (fix or feature that would cause existing functionality to not work as expected)
- Documentation Update (if none of the other choices apply)
Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.
- I have read the CONTRIBUTING.md doc.
- I have added necessary documentation (if appropriate).
- Any dependent changes have been merged and published in downstream modules.
Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...
Contributors
Assets 2
6.8.0
What’s Changed
Fix/doc @brunodasilvalenga (#55)
Contributors
Assets 2
6.7.0
What’s Changed
Update README.md @Aronyu127 (#42)
## Reason - The old input value seems be deprecated but not update to README.mdTypes of changes
What types of changes does your code introduce to <repo_name>?
Put an x in the boxes that apply
- Bugfix (non-breaking change which fixes an issue)
- New feature (non-breaking change which adds functionality)
- Breaking change (fix or feature that would cause existing functionality to not work as expected)
- Documentation Update (if none of the other choices apply)
Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.
- I have read the CONTRIBUTING.md doc.
- I have added necessary documentation (if appropriate).
- Any dependent changes have been merged and published in downstream modules.
Contributors
Assets 2
6.6.0
What’s Changed
remove deprecated template_file function @jkhan-mydeal (#51)
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.Types of changes
What types of changes does your code introduce to <repo_name>?
Put an x in the boxes that apply
- Bugfix (non-breaking change which fixes an issue)
- New feature (non-breaking change which adds functionality)
- Breaking change (fix or feature that would cause existing functionality to not work as expected)
- Documentation Update (if none of the other choices apply)
Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.
- I have read the CONTRIBUTING.md doc.
- I have added necessary documentation (if appropriate).
- Any dependent changes have been merged and published in downstream modules.
Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...
Contributors
Assets 2
6.5.0
What’s Changed
cluster settings deprecation fix @matthosking-mydeal (#47)
Deprecation warning fix - move to aws_ecs_cluster_capacity_providers setting as inline is deprecated.Types of changes
- Bugfix (non-breaking change which fixes an issue)
- New feature (non-breaking change which adds functionality)
- Breaking change (fix or feature that would cause existing functionality to not work as expected)
- Documentation Update (if none of the other choices apply)
Checklist
- I have read the CONTRIBUTING.md doc.
- I have added necessary documentation (if appropriate).
- Any dependent changes have been merged and published in downstream modules.
Contributors
Assets 2
6.4.0
What’s Changed
Clean up unnecessary file @lzrocha (#48)
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.Types of changes
What types of changes does your code introduce to <repo_name>?
Put an x in the boxes that apply
- Bugfix (non-breaking change which fixes an issue)
- New feature (non-breaking change which adds functionality)
- Breaking change (fix or feature that would cause existing functionality to not work as expected)
- Documentation Update (if none of the other choices apply)
Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.
- I have read the CONTRIBUTING.md doc.
- I have added necessary documentation (if appropriate).
- [ x] Any dependent changes have been merged and published in downstream modules.
Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...
Contributors
Assets 2
6.3.0
What’s Changed
🚀 Enhancements
Feature/auto release @mcosta1105 (#45)
Added GitHub actions workflow to automate releases based on PR labels when merged into master.Types of changes
What types of changes does your code introduce to <repo_name>?
Put an x in the boxes that apply
- Bugfix (non-breaking change which fixes an issue)
- New feature (non-breaking change which adds functionality)
- Breaking change (fix or feature that would cause existing functionality to not work as expected)
- Documentation Update (if none of the other choices apply)
Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.
- I have read the CONTRIBUTING.md doc.
- I have added the necessary documentation (if appropriate).
- Any dependent changes have been merged and published in downstream modules.
Further comments
If this is a relatively large or complex change, kick off the discussion by explaining why you chose the solution you did and what alternatives you considered, etc...
Contributors
Assets 2
6.2.0
What's Changed
- Update actions checkout by @mcosta1105 in #44
- Add container insights by @lzrocha in #46
New Contributors
- @mcosta1105 made their first contribution in #44
Full Changelog: 6.1.0...6.2.0
