Details
-
Bug
-
Resolution: Done
-
Critical
-
None
-
SaaS
-
False
-
False
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
No
-
Undefined
-
-
Description
Current behaviour
Proxy pro feature adds a redirect url field to the mapping rule object which should be editable in the UI but unfortunately the field does not render so this value cannot be updated after the mapping rule has been created.
Expected behaviour
Proxy pro feature adds a redirect url field to the mapping rule object which a user can edit in the UI.
Patching the deployment with the following steps fixes the issue:
- Create a file edit.html.slim that adds:
include_redirect: @service.using_proxy_pro?
- Create the ConfigMap:
oc create configmap edit --from-file=edit.html.slim
- Add the volume to system-app:
oc set volumes dc/system-app --add --overwrite --name=edit --mount-path=/opt/system/app/views/api/proxy_rules/edit.html.slim --sub-path=edit.html.slim --source='{"configMap":{"name":"edit"}}'
- Go to the admin portal and try to edit a mapping rule, the Redirect field is rendered now.