-
Notifications
You must be signed in to change notification settings - Fork 9.3k
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
Add option to allow no results when querying aws_instances Data Source #5055
Add option to allow no results when querying aws_instances Data Source #5055
Conversation
Hey there @coop182 ! Could you elaborate some on the possible use cases for this? The docs included mention "querying the count of ephemeral instances", how would you imagine this count is later used? Thanks 😄 |
Hey @catsby, This would be really useful when doing rolling ASG deploys as outlined here - which implements the strategy outline by @phinze here. Effectively being able to query the aws_instances data source without it throwing an error when no instances are found would allow it to be used to dynamically size the new ASG to the same size as the current ASG. For example if I have a min_size of 1 and max_size of 20 and a desired_capacity that moves between those numbers constantly via auto scaling policies at the moment I can see no way to set the new ASG to the exact desired capacity required at the point in time of the deploy... this leads to either having to over or under provision the number of instances on a rolling ASG deploy. Maybe I have missed a better way to do or think about this? Example code:
|
b3f61a5
to
9c81e9d
Compare
Pull request #21306 has significantly refactored the AWS Provider codebase. As a result, most PRs opened prior to the refactor now have merge conflicts that must be resolved before proceeding. Specifically, PR #21306 relocated the code for all AWS resources and data sources from a single We recognize that many pull requests have been open for some time without yet being addressed by our maintainers. Therefore, we want to make it clear that resolving these conflicts in no way affects the prioritization of a particular pull request. Once a pull request has been prioritized for review, the necessary changes will be made by a maintainer -- either directly or in collaboration with the pull request author. For a more complete description of this refactor, including examples of how old filepaths and function names correspond to their new counterparts: please refer to issue #20000. For a quick guide on how to amend your pull request to resolve the merge conflicts resulting from this refactor and bring it in line with our new code patterns: please refer to our Service Package Refactor Pull Request Guide. |
This functionality has been released in v4.0.0 of the Terraform AWS Provider. Please see the Terraform documentation on provider versioning or reach out if you need any assistance upgrading. For further feature requests or bug reports with this functionality, please create a new GitHub issue following the template. Thank you! |
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. |
Changes proposed in this pull request:
Output from acceptance testing: