HCL and YAML Options for Spinnaker Pipelines as Code (Dinghy)

We are excited to announce the initial release of an update for Pipelines as Code (Dinghy).

We now have YAML and HCL options to create templates with Dinghyfile. Adding YAML and HCL allows you to use a structured and more familiar way of defining Spinnaker pipelines as code.

The goal is to reduce context switching by having the language you're most comfortable with across toolsets.

To use one of these alternate formats, you’ll need to configure a local override with one of these parsers set in ~/.hal/default/profiles/dinghy-local.yml:

parserFormat: hcl

The parserFormat configuration only accepts the following values:

  • json (Default. There is no need to specify this if you want to keep using json.)
  • yaml
  • hcl

*Note: in the future, Armory will add this configuration to halyard cli.

For more details please check out our documents. We encourage and appreciate any feedback.

Armory's platform exists to help software teams ship better software faster. You can:

Enjoy!