Skip to content

v0.6.0: Merge pull request #52 from akamai/release/0.6.0

Choose a tag to compare

View all tags
@zstlaw zstlaw released this 18 Mar 20:12
· 22 commits to master since this release
v0.6.0
5451efd
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.
  • Minimum supported npm version updated to 6.13.4 to force deprecation of versions of npm with major security flaws.
  • Pipeline environment promotion now allows out of order promotions by default. --force is no longer needed for promotion when a previous environment has not yet promoted successfully.
  • Pipeline made changes to EnvInfo.json to fix conflicting status issues that hindered jenkins managed & multi-developer projects.
  • Account switching flag support enabled to better support teams with access to multiple Akamai accounts.

Detailed explanation of bug fixes in release contained below:

  • Creating a new pipeline based off of an existing property will properly retain the rule format of the source property.
  • Out of order environment promotion now allowed by default. Previously a user needed to promote each environment in series and If a later environment required a change to a template all earlier stages needed to get redeployed before the pipeline could continue. This requirement and the need to use --force to overrule it has been removed to make it easier for users to make decide if an issue is time critical or a change requires retesting in previous environments. The user now has more control over the deployment order and can skip environments when not needed. (Such as when a environment is still being used to test a different change but should not block a more time critical change from going forward to the next QA environment)
  • #37 - Fixed main source of conflicts in EnvInfo.json files. Removed EnvInfo etag field and no longer require it when making changes that create new property versions. This improves federated (multi-developer) development as well as Jenkins build server managed deployments where EnvInfo tended to get out of sync between developers. This should make it much less likely for a pipeline to get into a broken state.
  • When creating a new pipeline both single stage pipelines as well as pipelines with up to 30 environments are allowed. The number of allowed environments used to be limited to 2-10 but now supports pipelines with 1-30 environments.
  • Updated required npm version to 6.13.4 or higher disallowing earlier versions to force deprecation of versions with known major security flaw.
  • Account switching support added for teams with access to multiple Akamai Accounts.
  • #47 #51 - devopsSettings.json randomly deleted on promote.
Assets 2
Loading