You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Please vote on this issue by adding a 👍 reaction 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
Add the ability to restrict access to the key vault packer spins up by IP_Rules.
Use Case(s)
In my ENV we have policies that basically say don't allow "the world" access to KVTs. We have to use a predefined KVT for now, since packer wants to allow access to openly by default.
Potential configuration
A new config opt
build_key_vault_allowed_inbound_ip_addresses
Potential References
The text was updated successfully, but these errors were encountered:
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 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
Add the ability to restrict access to the key vault packer spins up by IP_Rules.
Use Case(s)
In my ENV we have policies that basically say don't allow "the world" access to KVTs. We have to use a predefined KVT for now, since packer wants to allow access to openly by default.
Potential configuration
A new config opt
Potential References
The text was updated successfully, but these errors were encountered: