When alertManager.spec.configSecret was present it didn't include the namespace which caused subsequent lookups of the secret to fail. This corrects the id by prefixing the namespace to it.
rancher/dashboard#1845rancher/dashboard#1805
- parentOverrides now part of type-map/configureType to set and type-map/optionsFor to get.
- Remove asyncData from resourceDetail flow
- Rehydrate fetch() data
- We just filtered out nameless routes which caused problems with default routes and manually created routes. This now gives a default name of `route-${i}` which if saved will add the name to the route.
- We remove the names before saving and prever the user from setting the name.
- Made the yamlSaveOverride consistent with receivers since it wasn't working when going to edit as yaml from the create page.
rancher/dsahboard#1239
The utility was broken in prod due to the function names changing. Instead of trying to differentiate the dispatch method being used we just set the { root:true } config so we can always use the 'cluster/action'.
https://github.com/rancher/dashboard/issues/1238#issuecomment-719730626
- Extracted code that could be shared between route and receiver into an alertmanagerconfig util
- Added some more support code to allow users to dynamically add/remove uncreatableTypes
rancher/dashboard#1239