Release notes
Back to All

Mar 18, 2020 — Property Manager CLI: Minor version release updates

over 5 years ago

The version 0.6 maintenance release of the Property Manager CLI updates.

  • Pipeline environment order. You can now update environments in any order you want without editing templates or using the --force argument. Out-of-order environment promotion is available by default.
  • Number of environments. The Property Manager CLI now supports pipelines with 1 to 30 environments. Previously, the CLI supported 2 to 10 pipelines.
  • Account switching support. added for teams with access to multiple Akamai accounts.
  • Support for npm. Updated npm support to version 6.13.4.
  • Bug fixes. Fixes to these issues:
    • New pipeline from existing property. Creating a new pipeline based off of an existing property now properly retains the rule format of the source property.
    • Status conflicts. Updated envInfo.json to prevent status conflicts for multi-developer and Jenkins-managed projects. The EnvInfo etag field was removed and is no longer required.

Property Manager CLI: Planned major version

The next major version of the Property Manager CLI is planned for this year. It’s expected to include these updates as well as others:

  • UI enhancements. The Property Manager UI will include an indicator when a property is managed by a pipeline.
  • Pipeline property locking. By default, you won’t be able to use PAPI or the Property Manager UI to edit properties managed by a pipeline. You’ll be able to override this default if needed.
  • Workflow support. Support will be added for more Property Manager workflows.