-
Notifications
You must be signed in to change notification settings - Fork 10
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 our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Migrate from Terraform to OpenTofu #104
base: main
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
First, thanks a lot for your PR!
This looks too simple to be true 😂 Did you test this somehow, by chance? Not sure, but who knows - maybe there is a way :)
So you think renaming this repository and then merging this PR should be enough? Or are there additional steps we need to take?
/plan |
@sprankhub Starting Terraform plan https://github.com/mage-os/terraform/actions/runs/12756324713 |
Terraform Plan
|
@davidtabat the "plan" above shows an error, even though it looks okay. Any idea? Do you think it will be gone when we rename this repository? |
genuine question: if we rename the repo, shouldn't we rename it to a platform-agnostic one like "infrastructure" or something like that? |
@sprankhub Yes I tested it. Described in the taiga ticket comment - how exactly https://tree.taiga.io/project/mage-os-mage-os-technical-initiatives/us/37?kanban-status=9349607 |
@fballiano Yes, agree with you, that indeed sounds better. |
I agree, but https://github.com/mage-os/infrastructure is taken already :D Other ideas?
|
I tested renaming on a dummy repo, and even after renaming it on GitHub, there were still errors due to the state saved in the backend. For now, I’ll take some time to figure out how to do it properly. 😄 Regarding the name, I think 'infrastructure-setup' is good. Maybe we should create a poll in Discord? Or is this too small of a matter to give so much attention to?" |
Are we sure that this switch won't result in a lock change or even worse in a re-creation of existing repos? |
So, for example, when we destroy the tf repo, can this have an impact on any other repos? |
@DavidLambauer It shouldn't, but I will test that here to be sure ofc: https://github.com/orgs/test-opentofu-mageos/repositories. |
I'm nobody to decide anything but I'm fine with infrastructure-setup
I sincerely hope TF doesn't work that way, is there a way to know? |
In the early days, I ran into some lock issues, and that's why I am asking. If it's properly tested, we should be fine I guess. |
As part of this PR, I renamed the terraform repository to opentofu in variables.tf for consistency.
Please ensure the repository on GitHub is renamed from terraform to opentofu before merging this PR. Otherwise, merging will trigger the creation of a new repository named opentofu.
If you don't want renaming the repository, let me know, and I will revert the name in variables.tf.