Execute an Op Script from a Remote Site
As an alternative to storing operation (op) scripts locally on the device, you can store op
scripts at a remote site. You then execute a
remote op script by issuing the
op
command and specifying the
url url
option. You can execute SLAX and XSLT op scripts
from a remote site by default. To execute Python
op scripts from a remote site, you must first
configure the
allow-url-for-python
statement at
the [edit system scripts op]
hierarchy level. Because you cannot guarantee that
scripts executed from remote sites are secure, we
recommend that you only authorize trusted users to
execute scripts using the op url
command.
Statements configured under the [edit system scripts op]
hierarchy level are
only enforced for op scripts that are local to the
device. Thus, even if you configure memory
allocation, script dampening, script start
options, traceoptions, or other op script-specific
statements within that hierarchy, the device does
not apply the configuration when you execute a
remote script using the op url
command.
To execute an op script from a remote site:
If you instead want to prevent the execution of any op scripts from remote sites, configure the
no-allow-url
statement at the [edit system scripts
op]
hierarchy level.
user@host# set system scripts op no-allow-url user@host# commit
When you configure the no-allow-url
statement, issuing
the op url url
operational mode command
generates an error. This statement takes precedence when the allow-url-for-python
statement is also present in the configuration.
Change History Table
Feature support is determined by the platform and release you are using. Use Feature Explorer to determine if a feature is supported on your platform.