This repository has been archived by the owner on Dec 26, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 44
Terraform version handling | dynamic updates #608
Comments
How does TFC handle this? |
leg100
added a commit
that referenced
this issue
Oct 13, 2023
leg100
added a commit
that referenced
this issue
Oct 20, 2023
🤖 I have created a release *beep* *boop* --- ## [0.1.14](v0.1.13...v0.1.14) (2023-10-19) ### Features * github app: [#617](#617) * always use latest terraform version ([#616](#616)) ([83469ca](83469ca)), closes [#608](#608) ### Bug Fixes * error 'schema: converter not found for integration.manifest' ([e53ebf2](e53ebf2)) * fixed bug where proxy was ignored ([#609](#609)) ([c1ee8d8](c1ee8d8)) * prevent modules with no published versions from crashing otf ([#611](#611)) ([84aa299](84aa299)) * skip reporting runs created via API ([#622](#622)) ([5d4527b](5d4527b)), closes [#618](#618) ### Miscellaneous * add note re cloud block to allow CLI apply ([4f03544](4f03544)) * remove unused exchange code response ([4a966cd](4a966cd)) * upgrade vulnerable markdown go mod ([781e0f6](781e0f6)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). --------- Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com> Co-authored-by: Louis Garman <75728+leg100@users.noreply.github.com>
Does this means that a new version of terraform would be picked up at every apply|plan|... of this workspace? |
The mechanics of how it works is slightly more complicated: a background
process checks for a new version every 24 hours and records it in the
database. That is the version a plan or apply uses.
…On Fri, Oct 20, 2023, 12:25 PM Daniel P ***@***.***> wrote:
Does this means that a new version of terraform would be picked up at
every apply|plan|... of this workspace?
—
Reply to this email directly, view it on GitHub
<#608 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAASPUF35PIV6YLQUJBOD2LYAJNRBAVCNFSM6AAAAAA5BOFA26VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZSGU3DENJZGQ>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
It is is concerning to me, as this can select a version with a bug and cause issues in the workspace. Multiple times Terraform core had bugs in it and caused issues. I understand that someone could want to use this feature, but an option to turn this off at org level and globally would be nice ( if not the case ). Im discussing here, I am not complaining here just sharing experience I had with Terraform. |
It's not the default behavior.
…On Fri, Oct 20, 2023, 2:17 PM Daniel P ***@***.***> wrote:
It is is concerning to me, as this can select a version with a bug and
cause issues in the workspace. Multiple times Terraform core had bugs in it
and caused issues.
I understand that someone could want to use this feature, but an option to
turn this off at org level and globally would be nice ( if not the case ).
Im discussing here, I am not complaining here just sharing experience I
had with Terraform.
—
Reply to this email directly, view it on GitHub
<#608 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAASPUDDTZUCTLOHG3KSRA3YAJ2VVAVCNFSM6AAAAAA5BOFA26VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONZSG4ZDIOJSGU>
.
You are receiving this because you modified the open/close state.Message
ID: ***@***.***>
|
👍 good then |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
We have a lot of workspaces meanwhile and changing the TF version in each of them becomes quite a task.
Removing the version from a workspaces, once set, is not supported at the moment. There is also no way to automatically use the latest TF version available AFAICS.
Proposal: allow to remove the hardcoded TF version field in a workspace and default to the latest available one?
Or alternatively allow to set an org-wide TF version for all workspaces.
The text was updated successfully, but these errors were encountered: