Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Question about using a TF Backend for Workspace Templates #17371

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

Closed
jatcod3r opened this issue Apr 11, 2025 · 0 comments
Closed

Question about using a TF Backend for Workspace Templates #17371

jatcod3r opened this issue Apr 11, 2025 · 0 comments

Comments

@jatcod3r
Copy link
Contributor

jatcod3r commented Apr 11, 2025

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:

Image

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.

@coder coder locked and limited conversation to collaborators Apr 14, 2025
@matifali matifali converted this issue into discussion #17386 Apr 14, 2025

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant