Editing a constraint's constraint template would require us to delete
the existing constraint and create a new one transactionally. Since
the backend doesn't support this transaction of we're disabling the ability
to edit which template is being used.
I also noticed a number of inconcictencies and poor behaviors
with the LabeledSelect component so I went ahead and made
it consistent with LabeledInput.
- The search field switched to a color distinct from the rest of the container
when disabled and hovered.
- There wasn't a focus outline.
- The size was slightly different because it was in a container
- There was a distinct background color around the arrow indicator
rancher/dashboard#433
secret type display in edit form
add custom secret types
description as prop in namens
secret styling
service account link in list view for service acct token secrets
We needed a way to support arbitrarily complex parameters in both
type and nesting level. As a temporary solution I enabled the user
to toggle between a key value component and a yaml editor.
To enable this I refactored ResourceYaml into a composable YamlEditor
component that can be used elsewhere.
rancher/dashboard#388rancher/dashboard#380
- Make system namespaces a part of the excluded namespaces match by default.
- Remove system namespaces from the options of namespace match
- Ensure that the types are getting edited appropriately.
rancher/dashboard#455rancher/dashboard#503
This implementst the view, create and edit pages for the
gatekeeper constraints. The constraint templates weren't
touched since we intend to only use the yaml editor.
rancher/dashboard#307