Closed rawlingsj closed 3 years ago
Some questions, do we want to tie the LTS version stream to a pipeline catalog revision? I think terraform modules may also need to be tied to the LTS version stream for when infra related changes are needed for features they are made available along with the LTS release.
I "think" this can be done fairly easily and maybe just with branches? Then an LTS release consists of version stream PR merged, terraform modules branch merged and possibly pipeline catalog branch merge?
This issue covers the UX for users switching between an LTS and latest release, so the command would be to swizzle whatever config we use above to change terraform, pipeline catalog branches and version stream repo.
This could be a
or
Which switches the version stream kpt file git repo. This should be enough?