-
Notifications
You must be signed in to change notification settings - Fork 45
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
ui: Fix configuration when changing the basePath and fix permissions management in the navbar #3254
Conversation
Hello jbwatenbergscality,My role is to assist you with the merge of this Status report is not available. |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
Peer approvals must include at least 1 approval from the following list:
|
/
/
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.
We also need to update the redirect URI in the Dex client configuration and in Shell UI configuration.
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
Peer approvals must include at least 1 approval from the following list:
The following reviewers are expecting changes from the author, or must review again: |
b080214
to
a36d3af
Compare
542e722
to
cde2685
Compare
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.
Only one thing blocking about leading/trailing slashes in Jinja templates, otherwise LGTM
salt/metalk8s/addons/ui/config/metalk8s-shell-ui-config.yaml.j2
Outdated
Show resolved
Hide resolved
4e7166f
to
c3fc82c
Compare
salt/metalk8s/addons/ui/config/metalk8s-shell-ui-config.yaml.j2
Outdated
Show resolved
Hide resolved
6a0e822
to
84c9576
Compare
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
Peer approvals must include at least 1 approval from the following list:
|
/approve |
Build failedThe build for commit did not succeed in branch bugfix/path-config. The following options are set: approve |
Waiting for approvalThe following approvals are needed before I can proceed with the merge:
Peer approvals must include at least 1 approval from the following list:
The following options are set: approve |
@@ -27,7 +27,7 @@ include: | |||
%} | |||
|
|||
{%- set stripped_base_path = metalk8s_ui_config.spec.basePath.strip('/') %} | |||
{%- set normalized_base_path = '/' ~ stripped_base_path if stripped_base_path else '' %} | |||
{%- set normalized_base_path = '/' ~ stripped_base_path if stripped_base_path else '/' %} |
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.
Maybe a stupid comment, but isn't this equivalent to
{%- set normalized_base_path = '/' ~ stripped_base_path %}
?
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.
done, I squashed and took care of it at the same time
…{{ metalk8s_ui_config.spec.basePath }}/shell/config.json As we have a nginx location rule on /shell/config.json in UI nginx, the path seen from there should be /shell/config.json instead of /{{ metalk8s_ui_config.spec.basePath }}/shell/config.json
ddfc72e
to
73c0adb
Compare
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.
Build failedThe build for commit did not succeed in branch bugfix/path-config. The following options are set: approve |
In the queueThe changeset has received all authorizations and has been added to the The changeset will be merged in:
The following branches will NOT be impacted:
There is no action required on your side. You will be notified here once IMPORTANT Please do not attempt to modify this pull request.
If you need this pull request to be removed from the queue, please contact a The following options are set: approve |
I have successfully merged the changeset of this pull request
The following branches have NOT changed:
Please check the status of the associated issue None. Goodbye jbwatenbergscality. |
Adding a `rewrite-target` annotation is needed when the base path is not /, because NGINX does not know where to find the documentation static files. We now always expose MetalK8s docs behind /docs, optionally appending the configured base path for MetalK8s UI (e.g. /docs/platform). This will avoid strange conflicts with the behaviour of the current Ingress when running MetalK8s at a non-root path, because mixing regular expressions and exact matches does not play well with ingress-nginx. See: #3254 See: https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/#use-regex
Adding a `rewrite-target` annotation is needed when the base path is not /, because NGINX does not know where to find the documentation static files. We now always expose MetalK8s docs behind /docs, optionally appending the configured base path for MetalK8s UI (e.g. /docs/platform). This will avoid strange conflicts with the behaviour of the current Ingress when running MetalK8s at a non-root path, because mixing regular expressions and exact matches does not play well with ingress-nginx. See: #3254 See: https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/#use-regex
Adding a `rewrite-target` annotation is needed when the base path is not /, because NGINX does not know where to find the documentation static files. We now always expose MetalK8s docs behind /docs, optionally appending the configured base path for MetalK8s UI (e.g. /docs/platform). This will avoid strange conflicts with the behaviour of the current Ingress when running MetalK8s at a non-root path, because mixing regular expressions and exact matches does not play well with ingress-nginx. See: #3254 See: https://kubernetes.github.io/ingress-nginx/user-guide/nginx-configuration/annotations/#use-regex
Component:
salt, ui
Context:
When deploying the UI on another path than
/
the shell-ui config couldn't be fetched.Also this PR brings a fix for the shell-ui which was checking if the user have all the groups instead of a single one to enable access to an entry.