feat(RHTAPWATCH-1038): Support custom certificate in ec pipeline #1288
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
lcarva
reviewed
Aug 12, 2024
Add ConfigMap parameters to support custom certificate in enterprise-contract pipeline. Jira-Url: https://issues.redhat.com/browse/RHTAPWATCH-1038 Signed-off-by: Homaja Marisetty <[email protected]>
hmariset
force-pushed
the
certificate-params
branch
from
bc7e238
to
ee3481d
Compare
lcarva
reviewed
Aug 13, 2024
lcarva
approved these changes
Aug 13, 2024
|
/retest |
github-merge-queue
bot
removed this pull request from the merge queue due to failed status checks
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.
Add ConfigMap parameters to support custom certificate in enterprise-contract pipeline.
Jira-Url: https://issues.redhat.com/browse/RHTAPWATCH-1038
Before you complete this pull request ...
Look for any open pull requests in the repository with the title "e2e-tests update" and
see if there are recent e2e-tests updates that will be applicable to your change.