Closed pennyscissors closed 3 years ago
The new scripts should allow us to declare Source branches in partner-owned repositories that validate against a Staging branch in our Rancher repository.
But based on recent conversation offline with @PennyScissors I think this is something we want to avoid since this makes reviewing partner-chart PRs and keeping them up to date with script versions / docs difficult to do.
I don't think this is something we can do since older Rancher releases still point to the older repo / naming schemes, so we can only create net-new branches and repositories that are referred to from now onwards.
So migrating partner-charts currently in rancher/charts and rancher/helm3-charts would mostly be copying them to a new repository / branch that would maintain them.
Closing because the plans for partner charts have changed due to a different team potentially taking over the projects.
Investigate how we can migrate all partner charts from our repositories into their own to simplify the submission process for them, and restructure our repositories/branching post migration.
Some important details to investigate:
rancher/charts
andrancher/helm3-charts
impact users?rancher/partner-charts
and separate by branches (feature-charts, helm2-charts, helm3-charts, or something like that)?rancher/charts
tolegacy-charts
and have feature charts as the default? Would it be better to migrate feature charts into a newrancher/feature-charts
repo, get rid ofrancher/helm3-charts
and userancher/charts
as our legacy charts repo with branches for each helm version?