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.
Fixes #367
Fixes #1003
The examples are currently integration tested, but against the code at skaffold HEAD. Configuration changes, such as v1alpha2 -> v1alpha3 will be present at HEAD, but not in the latest released version.
When users download the latest skaffold release, the examples are written for v1alpha3, but the latest release only targets v1alpha2 and below. Therefore, the examples will all fail, and users won't be able to skaffold fix, because the old version does not know about the new transformations. (skaffold fix only helps the situation of
old config, new skaffold
, where this isnew config, old skaffold
.We would like to keep our examples integration tested, so that they don't break for users. This PR makes
integration/examples
the canonical example repository. All changes are synced toexamples
on each release.This solves:
examples/
directory are runnable with the latest released version of skaffoldThis adds the sync to
release_note.sh
script, which might not be the best place for it.