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

Search for AWS AMIs #6862

Closed
beastie29a opened this issue May 24, 2016 · 5 comments
Closed

Search for AWS AMIs #6862

beastie29a opened this issue May 24, 2016 · 5 comments

Comments

@beastie29a
Copy link

Feature Request

Could the same functionality as the Ansible's ec2_ami_find module be added to the AWS provider?

https://docs.ansible.com/ansible/ec2_ami_find_module.html

Use Case:
Instead of updating a static AMI ID inside of a module, the "find" could grab the latest AMI each time by specifying the Owner ID, region and any other specific attribute such as virtualization type.

@vancluever
Copy link
Contributor

@beastie29a incidentally, I had an old PR for this: #4396, however it was held off on so that @apparentlymart could get in his #6598, which would enable this to be a first-class data source and not be subject to some issues during planning and applies in certain situations. If you need it in a pinch, I have been keeping my PR up to date and using it in our own configurations, but I will be starting work soon to refactor it as a new data source so it can get upstream, hopefully. Cheers!

@beastie29a
Copy link
Author

@vancluever I see it, don't know why it didn't come up in a search before, but it looks like exactly what I was requesting. I think I can go ahead and close this then.

@vancluever
Copy link
Contributor

I just finished refreshing this for data sources and will be putting in the PR shortly :)

@stack72
Copy link
Contributor

stack72 commented Jul 5, 2016

hi @beastie29a

I believe the data source work takes care of this :)

https://github.com/hashicorp/terraform/blob/master/website/source/docs/providers/aws/d/ami.html.markdown

P.

@stack72 stack72 closed this as completed Jul 5, 2016
@ghost
Copy link

ghost commented Apr 24, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants