feat: gpg #109
Open
feat: gpg #109
+23
−2
Conversation
This file contains 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
This was referenced Jun 28, 2024
vburckhardt
reviewed
Jul 3, 2024
| @@ -96,11 +96,23 @@ variable "watson_machine_learning_instance_resource_name" { | |||
| } | |||
|
|
|||
| variable "signing_key" { | |||
| description = "Signing GPG key." | |||
| description = "Signing GPG key. If it is not provided by the user, then automation will create one." | |||
There was a problem hiding this comment.
If this is optional, should this take a default?
There was a problem hiding this comment.
I don't think we can feasibly provide a "default" GPG key - either the user provides one, or the system generates one at apply time.
|
/run pipeline |
|
@vburckhardt @brendankellyibm can you please have a look into this PR? |
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.
Description
Release required?
x.x.X)x.X.x)X.x.x)Release notes content
Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
Checklist for reviewers
For mergers