You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not a blocker, but I was wondering if using a remote backend is allowed or not for workspace templates. I was experimenting with managing Terraform state in a remote S3 backend, but it doesn't look like this works with Coder:
My use-case was trying to see if it's possible to migrate an existing AWS EC2 VM into the platform, but it looks like it's expected that the Terraform state file is on the same directory as the project. For context, I'm using an external provisioner on EKS that has access to my S3 bucket backend, and it's currently on v2.20.1
Curious if this is intended or if there's something I'm missing on the documentation. I am aware about coder state pull and coder state push, but was wondering if it's possible to manage this without Coder needing to store the TF state in it's provisioner.
The text was updated successfully, but these errors were encountered:
Not a blocker, but I was wondering if using a remote backend is allowed or not for workspace templates. I was experimenting with managing Terraform state in a remote S3 backend, but it doesn't look like this works with Coder:
My use-case was trying to see if it's possible to migrate an existing AWS EC2 VM into the platform, but it looks like it's expected that the Terraform state file is on the same directory as the project. For context, I'm using an external provisioner on EKS that has access to my S3 bucket backend, and it's currently on
v2.20.1
Curious if this is intended or if there's something I'm missing on the documentation. I am aware about
coder state pull
andcoder state push
, but was wondering if it's possible to manage this without Coder needing to store the TF state in it's provisioner.The text was updated successfully, but these errors were encountered: