Skip to content

bug: Terraform provider can be upgraded ahead of Coderd and Provisionerd supportΒ #18048

Open
@spikecurtis

Description

@spikecurtis

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

When we introduce a new feature to terraform-provider-coder and release it, template authors can start writing templates with the feature immediately, even if their Coderd and Provisionerd have not been upgraded to correctly process the new feature.

At best, this can be confusing/frustrating, at worst, it could have cost or security implications where the template author thinks one thing is happening but it's actually another.

Relevant Log Output

Expected Behavior

Terraform providers should check the version of Provisionerd and/or the Provisionerd protocol, and fail builds if invoked features are unsupported.

Steps to Reproduce

Upgrade the Coder provider in a template and start using new features.

Environment

  • Host OS:
  • Coder version:

Additional Context

No response

Metadata

Metadata

Assignees

No one assigned

    Labels

    s2Broken use cases or features (with a workaround). Only humans may set this.

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions