...
All workflow execution properties are also available to the shell script, but any print of secure properties using echo command will result in ***** being printed in FlexDeploy logs. This prevents secure property values like passwords from being visible to any FlexDeploy user.
Inputs
Input Name | Input Code | Required | Description |
|---|---|---|---|
Code Snippet |
| Yes | The cmdlets and/or PowerShell scripts that are to be executed in a Windows environment. |
Restrict Environment |
| No | Provide comma-separated target group codes to restrict environment variables in shell to specified target group codes. If no value is provided all properties are available to shell environment. |
No Secure Variables |
| No | Check if you do not want to pass secure/encrypted properties in PowerShell environment. |
Lock Name |
| No | If a value is given, only a single simultaneous execution with the given name is allowed per endpoint. |
Artifacts
This operation delegates consumes/produces artifacts decision to the workflow developer. Check Consumes Artifacts on the workflow step editor if this operation requires artifacts to be delivered prior to execution of the script. Check Produces Artifacts on the workflow step editor if this operation creates artifacts. The artifacts folder is available via the FD_ARTIFACTS_DIR variable.
Endpoint Selection
This operation delegates endpoint selection to the workflow developer. The workflow editor will default the selection to "All", which selects all available endpoints associated to the Target. Selecting a specific resource will result in selection of endpoints associated to the Target which have that resource defined.
Endpoint Execution
This operation delegates endpoint execution to the workflow developer. The workflow editor will default to "Any", which will execute on any one of the selected endpoints, which will be randomly picked from selected endpoints or a specific endpoint where previous step may have executed. Changing this value to "All" to will result in execution on all selected endpoints.
Special Considerations
Environment Variables - to use an input in your code snippet, you must create an environment variable by prefixing the plugin variable with $env: in order for it to be used by Windows PowerShell. This method must also be applied when using any environment variables, such as JAVA_HOME or FD_INSTANCE_CODE. Any number of inputs or properties can be used.
...
| Code Block | ||
|---|---|---|
| ||
Stop-AzureRmVM -Name "VirtualMachine3" -ResourceGroupName "ResourceGroup5" -Force |
Appendix
| Anchor | ||||
|---|---|---|---|---|
|
...