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 other comments that do not add relevant new information or questions, 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
The only way to push an artifact to an hcp_packer_registry using packer CLI is to provide HCP_CLIENT_ID and HCP_CLIENT_SECRET credentials but there's no way to authenticate using workload identity federation
For visibility since I've addressed the other issue you opened, this one will likely need some internal discussion to understand the implications and how we can implement it.
Sorry if this takes a bit of time to be implemented, just want us to make sure we do it right!
Community Note
Description
The only way to push an artifact to an hcp_packer_registry using packer CLI is to provide
HCP_CLIENT_ID
andHCP_CLIENT_SECRET
credentials but there's no way to authenticate using workload identity federationUse Case(s)
CI/CD: Automating Packer Build with Github Actions
The text was updated successfully, but these errors were encountered: