Movatterモバイル変換


[0]ホーム

URL:


Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

feat: enable Terraform template-wide variables by default#8334

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Merged
mtojek merged 3 commits intomainfromdrop-feature-use-managed-variables
Jul 7, 2023

Conversation

mtojek
Copy link
Member

@mtojekmtojek commentedJul 6, 2023
edited
Loading

Related:coder/terraform-provider-coder#140

Changes:

  • drop logic responsible for processing coder provider flags, includingfeature_use_managed_variables
  • feature_use_managed_variables is considered to be the only mode. The flag isignored in the schema, and will be removed eventually.
  • update wording in docs

@mtojekmtojek self-assigned thisJul 6, 2023
@mtojekmtojek marked this pull request as ready for reviewJuly 6, 2023 10:53
Copy link
Member

@johnstcnjohnstcn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Should be marked as a breaking change:

feat!: enable Terraform template-wide variables by default

Apart from that, what will happen if someone attempts to use an existing template with the below stanza?

provider "coder" {  feature_use_managed_variables = "true"}

Will they be directed to removefeature_use_managed_variables?

@mtojek
Copy link
MemberAuthor

Apart from that, what will happen if someone attempts to use an existing template with the below stanza?

Nothing happens, the feature flag is just ignored, hence I was not convinced to mark it as a breaking change. Someday in the future, we will update the coder provider schema to block the flag. Then, the coder will complain about an unknown feature flag.

@johnstcn
Copy link
Member

Apart from that, what will happen if someone attempts to use an existing template with the below stanza?

Nothing happens, the feature flag is just ignored, hence I was not convinced to mark it as a breaking change. Someday in the future, we will update the coder provider schema to block the flag. Then, the coder will complain about an unknown feature flag.

Got it - that's fine. 👍

mtojek reacted with rocket emoji

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Shouldn't the Coder provider be bumped to 0.10.0? In all of the example templates?

Copy link
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

It is a valid point, but I'd rather do this in a separate PR as more examples will be affected.

matifali reacted with thumbs up emoji
Copy link
Member

@mafredrimafredri left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Looks good 👍🏻

##Managed Terraform variables
##Terraform template-wide variables

>⚠️ Flag`feature_use_managed_variables` is available until v0.25.0 (Jul 2023) release. After this release, template-wide Terraform variables will be enabled by default.
Copy link
Member

@mafredrimafredriJul 7, 2023
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

Should this mention the coder provider version as well? (Edit: On second thought, maybe not.)

Copy link
MemberAuthor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others.Learn more.

In theory, terraform-provider-coder still accepts thefeature_use_managed_variables, so maybe not overcomplicate it :)

@mtojekmtojek merged commit6468763 intomainJul 7, 2023
@mtojekmtojek deleted the drop-feature-use-managed-variables branchJuly 7, 2023 09:49
@github-actionsgithub-actionsbot locked and limited conversation to collaboratorsJul 7, 2023
Sign up for freeto subscribe to this conversation on GitHub. Already have an account?Sign in.

Reviewers

@matifalimatifalimatifali left review comments

@mafredrimafredrimafredri approved these changes

@johnstcnjohnstcnjohnstcn approved these changes

@bpmctbpmctAwaiting requested review from bpmct

Assignees

@mtojekmtojek

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

4 participants

@mtojek@johnstcn@mafredri@matifali

[8]ページ先頭

©2009-2025 Movatter.jp