-
Notifications
You must be signed in to change notification settings - Fork 1
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
s3 backend? #1
Comments
Hey Alex! Thats correct. We currently export a mk for local and remote in the package.dhall under lib. If youd like to contribute s3, id be happy to receive it. Otherwise, we can backlog and add it at a later date. Also, yes, only one in the org currently. |
looks like theres a dozen back ends possible. these arent generated from schema somewhere? |
they're not, they were hand coded at the time, and not exposed in the mk function. I am finding the s3 backend though in https://github.com/hashicorp/terraform/blob/main/internal/backend/remote-state/s3/backend.go, so those and that folder would likely be a great place to start automating against. |
Go give dev a shot now that it has s3, and let me know if it works |
Apologies, wasn't type checking with those changes. dev branch has the following example with s3 backend functioning. https://github.com/dhall-terraform/dhall-terraform-stdlib/blob/dev/examples/s3.dhall Links can be converted to use rawcontent or even a github cdn |
Hi @emattiza
Looking at porting some hcl to dhall-tf and it looks like we use an s3 backend.
The typing here seems to be local/remote only? is that right? Would s3 just be a 3rd option there?
Are you the only person here?
Thanks
Alex
The text was updated successfully, but these errors were encountered: