Add enable_content_trust_cosign option (matching api) #372
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
flbla
approved these changes
Sep 18, 2023
|
Hi, |
Signed-off-by: Pascal Patty <[email protected]>
ppa007asr
force-pushed
the
patch-enable-cosign
branch
from
460f172 to
33bad75
Compare
|
@flbla The DCO has been fixed |
|
@flbla Hello Florian, We could really use this PR to be merged. But its waiting for a second reviewer. Could you PM one of the other maintainers to ask if they can check and approve this? Many thanks in advance |
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.
We use terraform harbor provider to deploy our harbor resources. The option enable_content_trust_cosign was missing. (which is present in de harbor api)
Pull Request is to get this option into the terraform provider