Skip to content
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.

Sign up for GitHub

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

Already on GitHub? Sign in to your account

Jump to bottom

Terraform version handling | dynamic updates #608

Closed
pat-s opened this issue Sep 21, 2023 · 7 comments · Fixed by #616 or #606
Closed

Terraform version handling | dynamic updates #608

pat-s opened this issue Sep 21, 2023 · 7 comments · Fixed by #616 or #606

Comments

@pat-s
Copy link
Contributor

pat-s commented Sep 21, 2023

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.
@leg100
Copy link
Owner

leg100 commented Sep 21, 2023

How does TFC handle this?

@pat-s
Copy link
Contributor Author

pat-s commented Sep 22, 2023

TFC provides a version option "latest" besides specific release versions

image

@hoshsadiq hoshsadiq mentioned this issue Oct 7, 2023
Closed
@leg100 leg100 mentioned this issue Oct 13, 2023
Merged
leg100 added a commit that referenced this issue Oct 13, 2023
@leg100
feat: always use latest terraform version (#616)
83469ca 
Fixes #608
@github-actions github-actions bot mentioned this issue Oct 13, 2023
Merged
leg100 added a commit that referenced this issue Oct 20, 2023
@github-actions @leg100
chore(master): release 0.1.14 (#606)
abb7f0f 
🤖 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 <[email protected]>
@nokernel
Copy link

Does this means that a new version of terraform would be picked up at every apply|plan|... of this workspace?

@leg100
Copy link
Owner

leg100 commented Oct 20, 2023 via email

@nokernel
Copy link

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.

@leg100
Copy link
Owner

leg100 commented Oct 20, 2023 via email

@nokernel
Copy link

👍 good then

@github-actions github-actions bot mentioned this issue Jan 11, 2025
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
3 participants
@leg100 @nokernel @pat-s