validate-replicated-sdk test #4118
Merged
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
cbodonnell
force-pushed
the
cbo/sc-92357/validate-replicated-sdk
branch
from
7a8a158 to
308d27e
Compare
cbodonnell
changed the title
cbodonnell
commented
Nov 3, 2023
cbodonnell
force-pushed
the
cbo/sc-92357/validate-replicated-sdk
branch
from
066b561 to
9177384
Compare
cbodonnell
force-pushed
the
cbo/sc-92357/validate-replicated-sdk
branch
from
9177384 to
7b22fc8
Compare
sgalsaleh
approved these changes
Nov 7, 2023
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.
What this PR does / why we need it:
This PR adds a
validate-replicated-sdkworkflow that runs on-PR to test that the following scenarios work:The above is tested on kind and openshift clusters using CMX.
Which issue(s) this PR fixes:
https://app.shortcut.com/replicated/story/92357/e2e-tests-for-installing-the-sdk-with-kots
Special notes for your reviewer:
Steps to reproduce
Does this PR introduce a user-facing change?
Does this PR require documentation?