Most likely due to us using atmos 1.168.0 alongside v1.32.0 of the utils provider. Im sure if we used the latest atmos with the latest utils provider, it probably would have worked fine

we just re-released it again 30 mins ago, can you please try again?

is there a way to pin our providers using some kind of atmos yaml magic, perhaps https://atmos.tools/components/terraform/providers ?

it would be nice to do this, then we can use renovate to slowly bump versions

failed during terraform-plan, after init

i can’t share the stack manifest without getting some red-tape approvals

unless you folks have some way of anonymizing stack yaml

is there still going to be a 1.33 🙏

Doesn't talk about version pinning for your use case

We can add a separate doc for provider pinning

When you combine that with atmos file generate, those files can be written automatically

I think with the “generate”, we’d also need to run the atmos generate command in the pipeline

Since we’re kind of paving a new path here and using an ancient version, we’re a little reluctant to try the feature over just pinning the version manually, so we’ll go with that strategy for now, and then when time permits, poc the more scalable strategy, and probably do it with the latest version soon enough 🙂

But yes, for an old version, will need to use some other way :-)

I think this issue is relevant here https://github.com/cloudposse/terraform-provider-utils/issues/141

The minimum version now for the latest 1.x utils provider is atmos 1.207.x or 1.209.x https://github.com/cloudposse/terraform-provider-utils/blob/8aedc996bfeee9207b2d3b82e4f54526f70d8e91/go.mod#L6

you still need to check the template error (if it's the only error, should be easy to fix) and update atmos and provider version - you can't stay at the old version forever

i tried the atmos generation via claude and it failed 😞

POC failed. New error confirms a Terraform constraint I missed:

Error: Duplicate required providers configuration
A module may have only one required providers configuration.

Terraform does not merge required_providers blocks across .tf files. A module has at most one. My earlier "Terraform merges multiple required_providers blocks" claim was wrong.

What this means

The "centralize one provider via generate:, leave others in <http://versions.tf|versions.tf>" approach is impossible. The only ways to make this work would be:

1. Generate the entire <http://versions.tf|versions.tf> from YAML — delete each component's <http://versions.tf|versions.tf> and declare ALL providers (aws, null, local, utils, github, ...) in generate.versions.tf.json. Then leverage Atmos's inheritance/deep-merge so a baseline generate: block in stacks/orgs/org/_defaults.yaml carries utils, and component-level YAML adds the rest. Atmos merges the maps before rendering. Larger refactor; would need its own POC.
2. Use a string template in generate: — emit raw HCL via Go template. Same single-block problem; you'd still need to include all required_providers.

looks like there is a related issue here https://github.com/cloudposse/atmos/issues/1194

Because the linked issue, I don't believe is implemented.

Related PR https://github.com/cloudposse/atmos/pull/1841

should this work?

generate:
        <http://versions.tf|versions.tf>:
          terraform:
            required_providers:
              utils:
                source: cloudposse/utils
                version: "1.35.0"

Instead, try

versions_override.tf

He uses it extensively