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
Rundeck 4.17.0
I am using Cascade Remote Options feature.
One of my option is PROTOCOL which may be one of http or https (Drop-down window), but I can not use ${option.PROTOCOL.name} in the corresponding part of Remote URL. I even can not save such a job. Seems this is extra validation on hardcoded protocol;
I have some remote URLs for such options parametrized, including protocol and sub-path, but I can not use them because of two "features" above: all / and : (separators for protocol, path and port) are URLencoded + not passing the validation during job save;
Would be nice to have a way to escape this behaviour.
The text was updated successfully, but these errors were encountered:
Rundeck 4.17.0
I am using Cascade Remote Options feature.
PROTOCOL
which may be one ofhttp
orhttps
(Drop-down window), but I can not use ${option.PROTOCOL.name} in the corresponding part ofRemote URL
. I even can not save such a job. Seems this is extra validation on hardcoded protocol;ENDPOINT
, which contains path separators/
, but I can not use it correcty because of URL encode ${option.[name].value} in Cascading Remote Options #811 - all separators are encoded and resulting URL becomes invalid;/
and:
(separators for protocol, path and port) are URLencoded + not passing the validation during job save;Would be nice to have a way to escape this behaviour.
The text was updated successfully, but these errors were encountered: