-
-
Notifications
You must be signed in to change notification settings - Fork 82
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
Document OpenTofu Support #594
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.
LGTM 🙌
My aside re: a new tf
alias can be brought up via a GH issue if we find that we want to discuss that further.
@Gowiem there might be some confusion on aliases; they can be anything you want. Here's some suggestions by @nitrocode (they're aggressively short!)
Then what you can do is |
While defaults for everything are defined in the `atmos.yaml`, the same settings, can be overridden by Stack configurations at any level: | ||
|
||
- `terraform` | ||
- `components.terraform` |
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.
- `components.terraform` |
|
||
::: | ||
|
||
Once you've configured Atmos to utilize `tofu`—either by adjusting the default `terraform.command` in the `atmos.yaml` |
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.
Once you've configured Atmos to utilize `tofu`—either by adjusting the default `terraform.command` in the `atmos.yaml` | |
Once you've configured Atmos to utilize `tofu`— |
::: | ||
|
||
Once you've configured Atmos to utilize `tofu`—either by adjusting the default `terraform.command` in the `atmos.yaml` | ||
or by specifying the `command` for an individual component—provisioning any component follows the same procedure as |
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.
or by specifying the `command` for an individual component—provisioning any component follows the same procedure as | |
by specifying the `command` for an individual component—provisioning any component follows the same procedure as |
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.
please see comments
Co-authored-by: Andriy Knysh <aknysh@users.noreply.github.com>
Co-authored-by: Andriy Knysh <aknysh@users.noreply.github.com>
Co-authored-by: Andriy Knysh <aknysh@users.noreply.github.com>
Co-authored-by: Andriy Knysh <aknysh@users.noreply.github.com>
what
why