Armory Release v2.23.0 is GA – Highlighted Updates
There have been a number of exciting updates in the latest release of Armory. Highlighted updates include:
Artifacts – Helm repo indexes, Oracle Objects; Configuration – Dynamic Accounts, Canary analysis with Dynatrace; Deployment targets – AWS Lambda, Google App Engine; Load Balancers, Plugins V2 Framework, and UI improvements.
Helm repo indexes are now supported for artifacts
You can provide
helm/index as a type when specifying an artifact path.
Versions now supported in artifacts using Oracle Objects
In the artifact selection UI, you can use
# after the artifact to indicate the version you want to use. For example:
Spinnaker reads account definitions (cloud providers, CI, metric stores, etc.) from Spring properties. This works well in a world with a handful of accounts that rarely change but causes operational pain when provisioning accounts dynamically or with account information stored externally. See the Spinnaker Account Management proposal for details.
The following providers can support loading credentials dynamically:
Canary analysis with Dynatrace
See the Using Canary Analysis with Dynatrace guide for how to configure and use this new feature.
Deployment targets – AWS
externalID for granting access to your AWS resources to a third party
Spinnaker can assume a role into third party resources (delegated access) that require AWS external IDs. To configure an AWS provider, add the
externalId property when specifying the
assumeRole properties. For example:
aws: name: delegated-prod accountId: 1234 assumeRole: role/spinnaker externalId: "unique ID assigned to Armory"
Enabling AWS Lambda in configurations has changed
lambda.enabled key has now moved under
aws: lambda: enabled: true accounts: - name: test lambdaEnabled: true
aws: features: lambda: enabled: true accounts: - name: test lambdaEnabled: true
There have been several fixes for Launch Templates and for the Lambda provider. See the open source changelog.
Deployment targets – Google
Google AppEngine add deploy global configuration stage
This new stage was created in order to support various configuration settings for an app engine application. You can find these settings in Google Cloud’s Configuration Files content.
appengine supports cron configuration. You can update or deploy cron configuration similar to how you deploy services. This stage replicates the functionality offered and allows you to deploy cron, dispatch, index, and queue configuration files to your
Support for AWS cross zone load balancing for Network Load Balancers
Spinnaker now supports the AWS cross zone load balancing setting. You’ll see a new checkbox in the UI when configuring NLBs. This is turned on by default for new load NLBs.
Plugin V2 Framework
The v2 plugin framework is now in place! The V2 plugin framework simplifies configuration of plugins and includes many quality of life changes for plugin developers interested in making spring based plugins. See V2 Compatibility for details.
Support for Redis SSL connection paths
To turn on SSL, add an
redis:// in the connection string:
redis: connection: rediss://localhost:6379
Support for displaying colors in console outputs
Pipelines can now be triggered by Helm Charts when they are published