hashicorp / hashicorp/packer-plugin-azure
Put the temporary password in the keyvault too.
- 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
If you need to faultfind a build, you need the temporary password generated by Packer to RDP into the VM. As far as I know, this is currently only output if you thought to start with `-debug` (and pressed enter a bunch times). The azure-arm builder already creates an Azure KeyVault to store the winrm certificate. Could it also put a secret in there with the temporary password?
#### Use Case(s)
Any faultfinding of a Windows VM being built by Packer.
#### Potential configuration
```
```
#### Potential References
Contributor guide
Research direction
Start at the azure-arm builder and inspect how it creates the Azure KeyVault and stores the WinRM certificate. Determine where the Packer-generated temporary password is available and how a KeyVault secret should be created; done means the password is stored for faultfinding of the built Windows VM.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- azure, go
- Domain
- cloud, infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100