hashicorp / hashicorp/packer-plugin-amazon
Allow Amazon-Import to only import to S3
- Dominant language
- Go
- Stars
- 91
- Forks
- 141
- Avg merge
- 2d 18h
- Merged PRs (30d)
- 3
Description
Please search the existing issues for relevant feature requests, and use the
reaction feature
(https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/)
to add upvotes to pre-existing requests.
#### Community Note
Please vote on this issue by adding a 👍 [reaction](https://blog.github.com/2016-03-10-add-reactions-to-pull-requests-issues-and-comments/) to the original issue to help the community and maintainers prioritize this request.
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request.
If you are interested in working on this issue or have submitted a pull request, please leave a comment.
#### Description
Requesting to be able to have 'Amazon Import' post-processor to upload a created image to S3, skipping the AMI conversion step.
Many people are starting to use S3 as a 'static' content library for vSphere. Being able to have packer create images and dump them directly to an S3 bucket would be great.
#### Use Case(s)
Any customer that often builds and destroys vSphere environments are starting to use S3 as a static content library for vCenter.
#### Potential configuration
```
```
#### Potential References
Contributor guide
Assessment
This issue has not been assessed yet.