AWS CodePipeline supports parameterized pipelines

Today, AWS CodePipeline announces the general availability of parameterized pipelines, a new feature that enables customers to dynamically pass input parameters to a pipeline execution. For a pipeline to accept input parameters, customers have to declare the variables and use them in action configurations. When releasing a change through the console, customers can set values for variables to use in the pipeline execution. These input variables can be used in configuration of all action types except Source action types. Customers can also set the values for the input parameters when starting a pipeline through API, CLI, SDK and CDK. Parameterized pipelines are available only with the new V2 pipeline type. Pipelines that don’t have a pipeline type set will default to V1, and will only include all previously available features. V2 pipeline type have different features and pricing. When you create or update a pipeline with the new V2 type, your pipeline can use input parameters and the pipeline execution history will show the variables that were provided for that pipeline execution. To learn more about the new pipeline type, included features, and billing implications, visit the [documentation](https://docs.aws.amazon.com/codepipeline/latest/userguide/pipeline-types.html). AWS CodePipeline is a fully managed [continuous delivery](https://aws.amazon.com/devops/continuous-delivery/) service that helps you automate your release pipelines for fast and reliable application and infrastructure updates. CodePipeline automates the build, test, and deploy phases of your release process every time there is a code change, based on the release model you define. To use parameters with AWS CodePipeline, visit our [documentation](https://docs.aws.amazon.com/codepipeline/latest/userguide/reference-variables.html). For more information about AWS CodePipeline, visit our [product page](https://aws.amazon.com/codepipeline/).