01-13-2025 10:47 AM
To fix this, you need to set the allow_duplicate_names parameter to true in your deployment configuration. This parameter allows the deployment to proceed even if the pipeline name conflicts with an existing pipeline.
allow_duplicate_names
true
View solution in original post
