CodePipeline supports additional trigger filters and new execution modes

AWS CodePipeline V2 type pipelines now support additional pipeline trigger filters, and two new pipeline execution modes: Parallel and Queued. Pipeline trigger filters enable customers using sources from GitHub.com, GitHub Enterprise Server, Bitbucket.com, GitLab.com, and GitLab self-managed to control when a pipeline execution should be triggered. Pipeline execution modes enable customers to control the concurrency behavior when multiple executions of a pipeline are started. Customers can define triggers for a pipeline using filters on Git event types such as push and pull request, and Git metadata such as branch names and file paths. For feature branches and GitFlow, customers can configure glob patterns on branch names, and for mono repos, customers can configure glob patterns on file paths. Parallel execution mode allows each execution of a pipeline to run in parallel without impacting other executions of the same pipeline, and Queued execution mode allows each execution of a pipeline to progress through the pipeline in the order in which it started, and more recent executions do not override it. To learn more about using pipeline triggers and pipeline execution modes, visit our [documentation](https://docs.aws.amazon.com/codepipeline/latest/userguide/execution-modes.html). For more information about AWS CodePipeline, visit our [product page](https://aws.amazon.com/codepipeline/). The new feature is available in all regions where AWS CodePipeline is supported except in the Asia Pacific (Hong Kong), Africa (Cape Town), Middle East (Bahrain), Europe (Zurich), Asia Pacific (Jakarta), Asia Pacific (Hyderabad), Asia Pacific (Osaka), Asia Pacific (Melbourne), Israel (Tel Aviv), Europe (Spain), and Middle East (UAE), and the AWS GovCloud (US-West) Regions.