Support passing API Signing Key from the memory #131
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
|
Hi, @lbajolet-hashicorp, you have recently helped us (@obabec) to merge an addition of |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi, I would like to add the option to provide the OCI API Signing Key directly from the memory by adding a
keyattribute. This is already supported by the OCI Terraform provider and is useful when running Packer from CI/CD. Thekeyis not inteded to be checked into the source control, but rather dynamically fetched from a secrets manager system. Setting thekeyoverrideskey_fileconsistently with the documented behaviour of the OCI Terraform provider.Additionally, small refactor and improvements of the surrounding comments and error messages were done.