hashicorp / hashicorp/packer-plugin-azure
New Key Vault opt to only allow certain IPs
- Dominant language
- Go
- Stars
- 63
- Forks
- 103
- PR merge metrics
- No merged PRs in 30d
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
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
Contributor guide
Research direction
Start by locating the Azure Key Vault creation path and the configuration handling for the proposed build_key_vault_allowed_inbound_ip_addresses option. Check existing tests around Key Vault setup, then confirm that the configured IP rules are applied and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, go
- Domain
- cloud, security
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100