-
Notifications
You must be signed in to change notification settings - Fork 49
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
feat: Open id connect resource view #3739
base: main
Are you sure you want to change the base?
feat: Open id connect resource view #3739
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
presets: |- | ||
- name: template | ||
default: true | ||
value: | ||
metadata: | ||
annotations: | ||
authentication.gardener.cloud/class: garden |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think it's necessary
- source: spec | ||
name: Specification JSON | ||
widget: CodeViewer | ||
language: "'json'" | ||
- source: metadata | ||
name: Metadata | ||
widget: CodeViewer | ||
language: "'json'" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Metadata is in the header, spec is in Panel, it's not so necessary.
header: | ||
- source: metadata.name | ||
name: Name |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This also could be removed.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You are adding this file in new directory, so to build it in Busola you need to add it into extensions.json
files for dev, stage and prod
source: spec.clientID | ||
form: |- | ||
- path: spec.issuerURL | ||
visibility: $not((metadata.labels."operator.kyma-project.io/managed-by") = "infrastructure-manager") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this couldn't be done as visibility, because the user still can mess up in YAML, this should be done in disableEdit
in general section.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- false | ||
- path: spec.supportedSigningAlgs | ||
visibility: $not((metadata.labels."operator.kyma-project.io/managed-by") = "infrastructure-manager") | ||
overwrite: false |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What this flag is doing? I don't think it's necessary.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
When visibility is set to false I saw that all fields is somehow overwrite by this and it detects that there are some changes (probably if visibility is false all fields are clearing). This flag prevents this changes but will be not needed if I'll remove visibility and use disableEdit like you suggested.
Description
Changes proposed in this pull request:
Related issue(s)
Closes #3651
Definition of done
backlog#4567