do not sync config on changes on main; do it only releases #2305
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 issue type does this pull request address? (keep at least one, remove the others)
/kind enhancement
What does this pull request do? Which issues does it resolve? (use
resolves #<issue_number>
if possible)removes
sync-config.yaml
workflows, that was copying theconfig/*.go
contents tovcluster-config
on each change.As the result, there was potential mismatch between
vcluster.schema.json
&config/*.go
files invcluster-config
.Instead, we will generate
vcluster.schema.json
on each release & copy contents ofconfig/*.go
files on one commit.Then, we can tag this commit with given minor version in the
vcluster-config
repo.