SidHeg
commented
4 years ago If properties, which are part of a pipeline are modified using tools other than the PM-CLI pipeline command, they cannot be used again by PM-CLI pipeline. Trying it would give errors. The best option is to create a new pipeline (with old pipeline name) with existing properties.
Steps for that: Note down the names and order of the old pipeline properties. Delete or Move the old pipeline folder and its contents. Create a pipeline (with the old pipeline name) with the option [--associate-property-name] and pass in the old pipeline’s properties’ names as arguments in the same order.
Things to remember: Order of properties – is the order in which the environment names were passed during the creation of the original pipeline Use the complete property name as arguments for [--associate-property-name]. For example, if the property names are “dev.pipeline.com” or “prod.pipeline.com” use these names and not just “dev” or “prod”.
I created a pipeline with "dev" and "prod" environments and promoted version 1 of "dev" env through "akamai pipeline promote"
I updated the cache TTL in "main.json" and did the merge. As a result a new version on ACC was created, which I deployed via Akamai Control Center.
Now, if I updated any other rule in the snippets - say another cache update and try to promote it via akamai pipeline, I get an error that "version 2 is already active"
How can sync envInfo.json to reflect the latest changes? Or may be create version 3 using pipeline.