Feat(addon): addons managed by an Application, and Config CRDs on the Configs pages (8/21)

Merged
BR
16d ago
+1093-38

Stack 8/21 · after #959 · next #961

Targets main but builds on #959, so the earlier stack commits show here too: review the last commit only. Merge after #959.

Description of your changes

  • An addon that an Application manages (KubeVela 1.12's addon component) is left to that Application: its status names the managing Application, and Enable, Upgrade and Disable refuse it with an error saying so. Before, Disable deleted the addon's Application out from under its parent.
  • The Configs pages read ConfigTemplate and Config CRDs alongside the legacy secrets, keeping a Config's templateRef as written on update. A config's alias is its own column.

08-configs

Fixes #

I have:

  • Read and followed KubeVela's contribution process.
  • Related Docs updated properly. In a new feature or configuration option, an update to the documentation is necessary.
  • Run yarn lint to ensure the frontend changes are ready for review.
  • Run make reviewableto ensure the server changes are ready for review.
  • Added backport release-x.y labels to auto-backport this PR if necessary.

Special notes for your reviewer

  • Legacy secret-backed configs keep working; CRD-backed ones are listed with them.