You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When the no proxy host name list is locked (via deployment policies), it's not correctly locked in the UI; it's still possible to modify the multi-line text area holding the list (but it's not possible to actually submit the changes).
Steps to Reproduce
Factory reset (this creates a default no-proxy list).
Start Rancher Desktop.
Run rdctl create-profile --from-settings --output reg --type locked --hive hkcu | Out-File -Encoding utf8 .\settings.reg to generate a deployment profile.
Double click the newly generated settings.reg and import it into the registry.
Start Rancher Desktop
Go to Preferences → WSL → Proxy
Try to edit the no proxy list.
Result
It is possible to edit the list; there is no indication that the preference is locked.
Expected Behavior
The list should be disabled (as in, the user should not be able to edit it).
Would is be possible to fix it as part of #5344 or will the fix be needed earlier?
It should be fixed as part of #5344. This is not a critical issue as validation still prevents you from applying the setting after you changed it from its locked value. This is not good UX, but does not violate the promise of the locked profile.
Actual Behavior
When the no proxy host name list is locked (via deployment policies), it's not correctly locked in the UI; it's still possible to modify the multi-line text area holding the list (but it's not possible to actually submit the changes).
Steps to Reproduce
rdctl create-profile --from-settings --output reg --type locked --hive hkcu | Out-File -Encoding utf8 .\settings.reg
to generate a deployment profile.settings.reg
and import it into the registry.Result
It is possible to edit the list; there is no indication that the preference is locked.
Expected Behavior
The list should be disabled (as in, the user should not be able to edit it).
Additional Information
This will probably be obsoleted by #5344
Rancher Desktop Version
1.10-RC1 (0dd5a25)
Rancher Desktop K8s Version
N/A
Which container engine are you using?
containerd (nerdctl)
What operating system are you using?
Windows
Operating System / Build Version
Windows 11 Pro 22H2 (Build 22621.2134)
What CPU architecture are you using?
x64
Linux only: what package format did you use to install Rancher Desktop?
None
Windows User Only
None (fresh VM).
The text was updated successfully, but these errors were encountered: