The read-only Function name field displays the function that is called in the pipeline.
Select an existing artifact resource from your DevOps project. The artifact must be generic (universal) file type. Parameters in the artifact must be in JSON format and can have placeholders. You must select the Allow parameterization check box when configuring the DevOps artifact resource to substitute the placeholders with the argument value during deployment. For more information, see Configuring Parameters.
Here's an example of the generic artifact content to pass two user-defined parameters and their values:
test_name
, app_version
{"test_name":"verify_production", "app_version":"${app_version}"}
If you select Run asynchronously, the service invokes the function but does not wait for the function to complete. On selecting Run synchronously, the service invokes the function and waits for the function to complete.
If the validation is enabled, then the service verifies the return value of the function. The return value is a UTF-8 string literal, true
or false
. If the return value is true
, then the stage is marked as Succeeded, otherwise the stage is marked as Failed.
If the validation is disabled, then the service does not verify the return value.
Validation occurs only if you have selected the option "Run synchronously" for stage run mode.
If you have permissions to create a resource, you also have permissions to add free-form tags to that resource.
To add a defined tag, you must have permissions to use the tag namespace.
For more information, see Resource Tags.
To automatically trigger a deployment from the build pipeline, you can add a Trigger Deployment stage to the build pipeline.
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4