Skip to content

v0.7.0-alpha: Updated schema and component names, added community folder, new command line options

Pre-release
Pre-release
Compare
Choose a tag to compare
@heyealex heyealex released this 03 May 21:20
· 6281 commits to main since this release
20481b4

Key New Features

  • Updated HPC Toolkit naming and schema with significant interface changes (read more below)
  • Moved community contributions to community folder
  • Overwrite flag (-w) optionally overwrites existing deployment folder while maintaining terraform state
  • Terraform Backend can be configured from command line (--backend-configs)
  • Recognition of the output of ghpc as a deployment, rather than blueprint: ghpc create now creates a folder with deployment_name instead of blueprint_name

Naming changes

  • Config YAML or Input YAML is now referred to as the HPC Blueprint
  • Resource Groups are now Deployment Groups
  • Blueprint Folder is now Deployment Folder
  • Resources are now HPC Modules
  • simple-instance is now vm-instance - Underlying module is the same

Blueprint YAML Schema Update

  • vars.deployment_name is used by ghpc for creating the deployment folder name, rather than blueprint_name
  • resource_groups is now deployment_groups
  • resources is now modules, and modules are stored in modules/ and community/modules/
  • Sourcing embedded modules starts with modules or community/modules

Example:

deployment_group:  # Was resource_groups:
  modules:  # Was Resources
  - source: modules/... # Was `- source: resources/...`

Improvements

  • Addition of "Community" folder
  • Overwrite option (-w) for creating a deployment in the same directory, retaining the terraform state and keeping a backup of one prior deployment.
  • Improved instructions for deploying after create
  • Support for startup-script with Packer resource
  • Command Line Flag for specifying terraform state backend config (--backend-config)
  • More reliable project ID validation

What's Changed

Full Changelog: v0.6.0-alpha...v0.7.0-alpha