Priority as string about terraform-provider-buildkite HOT 3 CLOSED

Oh right okay 👍

This isn't specific to this provider as the steps field is treated as a string. The priority field of the pipeline yaml cannot be non-numeric for the steps stored against the pipeline because the steps are not evaluated at runtime. So you'll need to interpolate that string with your environment variables in terraform before/during the apply so that by the time it gets uploaded to the API it looks like priority: 0.

It's the same sort of thing as if you called buildkite-agent pipeline upload <<YAML

from terraform-provider-buildkite.

Hi @fa93hws, I'm not sure where this fits into the terraform provider. We don't have any configuration for priority. Can you provide a more complete example of this issue for us to look at?

from terraform-provider-buildkite.

Hi thanks for the quick reply. I can not provide a CI link because it's internal sorry. What I have done is

  # language=yaml
  steps = <<YAML
env:
  ${local.env}
steps:
  - xxxx
    label: "xxxx"
    priority: $${STEP_PRIORITY_KICKSTART:-0}
    agents:
      - "xxxx"

And then I got the following error during apply saying:

Error: One of the steps you provided was invalid: is not a number

This error vanish once I change priority: $${STEP_PRIORITY_KICKSTART:-0} to priority: 1

from terraform-provider-buildkite.