Posted On: Nov 14, 2019
You can now pass variables from one action to another in your pipeline. Previously, there was no first-class support for passing metadata between actions during an execution. You can now dynamically configure your actions with variables that will be evaluated at execution time.
During a pipeline execution, you can now access variables produced by select action types or default variables made available at the start of each pipeline execution. For example, you can use the commit message output from a CodeCommit source action to set a custom message in your manual approval action. You can also generate and export an endpoint URL from a build job and run tests against it in a following test action. For custom workflows, you can output any variables from a Lambda action to be used in subsequent actions.
To see a list of all the regions where CodePipeline is available, please check out the AWS global region table.