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.

Sign up for GitHub

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

Jump to bottom

Handle properties fallback when running in client mode #1907

Merged
merged 1 commit into from
Jan 18, 2021
Merged

Handle properties fallback when running in client mode #1907

merged 1 commit into from
Jan 18, 2021

Commits on Jan 18, 2021

  1. Handle properties fallback when running in client mode 

    When the Dashboard frontend is running in client mode (i.e.
`kubectl proxy --www...`), set the fallback values for the
install properties (e.g. ReadOnly, IsTriggersInstalled) so
the Dashboard is more useful in this case.

Future updates will add more fine-grained access checks so
we only display options that are actually available depending
on the user's permissions.
    @AlanGreene
    AlanGreene committed Jan 18, 2021
    Configuration menu
    Copy the full SHA
    176f04d View commit details
    Browse the repository at this point in the history