-
Notifications
You must be signed in to change notification settings - Fork 25
"BEGIN PGP ARMORED FILE" -> "BEGIN PGP PUBLIC KEY BLOCK" for Go #15
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
"BEGIN PGP ARMORED FILE" -> "BEGIN PGP PUBLIC KEY BLOCK" for Go #15
Conversation
|
Why aren't we using the support for multiple keys in the ConfigMap to have them distinct there rather than the ad-hoc concatenation? |
Does the CVO already support that? |
|
Multiple keys in configmap is an AND. Multiple keys in a keyring is an OR. Beta2 and gold key are an OR until we get rid of beta2 key. |
Go's parser requires the well-known labels [1,2]. [1]: https://github.com/golang/crypto/blob/20be4c3c3ed52bfccdb2d59a412ee1a936d175a7/openpgp/keys.go#L244 [2]: openshift/cluster-version-operator#196
55054e6 to
eab0d87
Compare
|
/retest |
|
/lgtm |
|
/approve |
|
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: abhinavdahiya, eparis, wking The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Go's parser requires the well-known labels (openshift/cluster-version-operator#196).