Elastic Compute Service:Use a script interpreter to run Cloud Assistant commands

Specify the script interpreter

To specify the script interpreter in the Launcher parameter, follow one of these methods, depending on whether the absolute path of the interpreter is configured in the PATH environment variable:

• Environment variable not configured: Enter the absolute path of the specified script interpreter in the Launcher parameter. For example, the path of the Python script interpreter is not configured in the PATH environment variable, configure the Launcher parameter as follows:

  /usr/bin/python

• Environment variable configured: Enter the name of the interpreter in the Launcher parameter. For example, if the path of the Python script interpreter is in the PATH, specify it as python in the Launcher parameter:

  python

Use the identifier to specify the position of the script file in the command

• Identifier not specified

  Cloud Assistant appends the actual script file path to the end of the command. For example, if the Launcher is set to python, Cloud Assistant will run python <file> within the instance. <file> indicates the actual file path of the script, corresponding to the script content specified in CommandContent.

• Use the identifier to specify the position of the script file in the command

  For certain script interpreters that mandate a specific placement of the script file path within the command, such as the python interpreter which requires the script file path as the first parameter, the position of the script file can be specified by using the {{ACS::ScriptFileName}} identifier within the Launcher parameter. For example:

  python {{ACS::ScriptFileName}} arg1 arg2

  Cloud Assistant runs the command python <file> arg1 arg2 within the instance, where <file> is the actual path to the script, corresponding to the CommandContent.

• Use the identifier to specify the extension of the script file

  For script interpreters that require specific file extensions, the file extension can be specified by using the {{ACS::ScriptFileName|Ext(.ext)}} identifier. For example:

  python3 {{ACS::ScriptFileName|Ext(.py)}}

  In this case, Cloud Assistant replaces {{ACS::ScriptFileName|Ext(.py)}} in the Launcher parameter with the path of the script file, appending the .py extension. Cloud Assistant runs the command python3 <file>.py within the instance, where <file> is the actual file path to the script specified in CommandContent.

Invoke the Python program in the system to run a script

CommandContent

import datetime
current_date = datetime.date.today()
print(current_date)

Launcher

python {{ACS::ScriptFileName|Ext(.py)}}

Invoke the kubectl program in the system to run a script

CommandContent

apiVersion: v1
kind: Pod
metadata:
  name: my-pod
  labels:
    app: my-app
spec:
  containers:
  - name: my-container
    image: nginx
    ports:
    - containerPort: 80

Launcher

kubectl apply -f {{ACS::ScriptFileName|Ext(.yaml)}}

Invoke regedit to run the registry script

CommandContent

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Micorsoft\Windows\Persionalization]
"NoLockScreen"=dword:000000001

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control]
"WaittoKillServiceTimeout"="2000"

Launcher

regedit import {{ACS::ScriptFileName|Ext(.reg)}}