Is there plans to update pipeline template resource to use native HCL schema

[KeisukeYamashita]

What

Currently, pipeline and pipeline_template load JSON file. Are there plans to make theses to native HCL schema?

What

With HCL schema support, we can get diffs, validate inputs and so on.

[max-rocket-internet]

It would be good to have this but you can use jsonencode now to go from HCL to pipeline data. I tested it and it works well, for example:

resource "spinnaker_pipeline" "load_test" {
  for_each    = local.load_tests
  application = "xxxx"
  name        = "${each.key}-testing-do-not-use"
  pipeline    = jsonencode(local.pipeline_json)
}

locals {
  pipeline_json = {
    appConfig = {}
    isNew = true
    keepWaitingPipelines = false
    limitConcurrent = false
    notifications = []
    parameterConfig = [
      {
        default = "opa"
        description = "The name of the load test in Locust"
        hasOptions = true
        label = "loadtest_name"
        name = "loadtest_name"
        options = [
          {
            value = "myapp"
          }
        ]
        pinned = true
        required = true
      }
    ]
    stages = []
    triggers = []
  }

Also, even when using templatefile, you still get nice diffs of the JSON 🙂