Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Create simple migration script for smooth upgrade to next Korifi release #3672

Closed
georgethebeatle opened this issue Dec 20, 2024 · 0 comments
Labels

Comments

@georgethebeatle
Copy link
Member

Dev Notes

  • For next release we have prepared some breaking changes such as making resource list operaions dependent on a special label that has the resource namespace name as value.
  • It should be easy to create a script that patches all resources by labelling them with their namespace with the new korifi.cloudfoundry.org/space-guid label key
@github-project-automation github-project-automation bot moved this to 🧊 Icebox in Korifi - Backlog Dec 20, 2024
@georgethebeatle georgethebeatle moved this from 🧊 Icebox to 🇪🇺 To do in Korifi - Backlog Dec 20, 2024
@georgethebeatle georgethebeatle moved this from 🇪🇺 To do to 🔄 In progress in Korifi - Backlog Jan 17, 2025
danail-branekov added a commit that referenced this issue Jan 20, 2025
This hook labels Korifi existing resources (`cfapps`, `cfbuilds`,
`cfpackages`, `cfprocesses`, `cfroutes`, `cfservicebindings`,
`cfserviceinstances`, `cftasks`) with the
`korifi.cloudfoundry.org/space-guid` label. This label is needed to
adopt improvements in resource listing (see #3636)

The hook runs on pre-upgrade only, as it only make sense in an upgrade
scenario.

fixes #3672

Co-authored-by: Yusmen Zabanov <[email protected]>
Co-authored-by: Danail Branekov <[email protected]>
@github-project-automation github-project-automation bot moved this from 🔄 In progress to ✅ Done in Korifi - Backlog Jan 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Done
Development

No branches or pull requests

1 participant