Add sample versions in extraDevfileEntries.yaml #254
Merged
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 does this PR do?:
This PR is the last step to the support of multiple sample versions inside the
extraDevfileEntries.yaml
. This feature will allow us to support samples with parents using outerloop and to have more consistent ports.As a result all entries inside the
extraDevfileEntries.yaml
have been updated to have versions. Other than that the 3 samples that have a parent supporting outerloop now have an extra version. Those are:go-basic
: We have added version2.0.0
in order to support the outerloopgo
stack versions.python-basic
: We have added version2.0.0
in order to support the outerlooppython
stack versions.java-springboot-basic
: We have added version2.0.0
in order to support the outerloopjava-springboot
stack versions.Which issue(s) this PR fixes:
fixes devfile/api#1112
PR acceptance criteria:
Have you read the devfile registry contributing guide and followed its instructions?
Does this repository's tests pass with your changes?
Does any documentation need to be updated with your changes?
Have you tested the changes with existing tools, i.e. Odo, Che, Console? (See devfile registry contributing guide on how to test changes)
How to test changes / Special notes to the reviewer:
Some notes for the consumers of the registry:
ODC
is using the/index/sample
endpoint which will only return the default (old) versions of each sample.RHTAP
is using the/index/sample
endpoint which will only return the default (old) versions of each sample.odo
is not using the devfile samples.For
RHTAP
I've tried to update locally the mock-devfile-data.ts with the updatedindex/sample
(only thegit.revision
is added) and ran the tests. The tests were ok.For
ODC
I've started a console server locally (CRC) using minikube & a build of the updated registry.