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
When using tflocal, an s3 backend is generated automatically to use the localstack endpoints for the remote state. This works in many cases, however if the desired backend configuration has been customized beyond the default options/configuration applied in TF_S3_BACKEND_CONFIG (https://github.com/localstack/terraform-local/blob/main/bin/tflocal#L45), those options/configurations are lost.
For example, if the desired backend configuration has force_path_style = true, that configuration is lost when tflocal is used.
This is the initial backend configuration from the tf files.
Hi @mviamari!
You are right, currently these configurations are not merged into the backend block.
We'd ask your patience to add this issue to our timeline and implement the changes you've requested. I'll get back to you soon with more information.
When using
tflocal
, an s3 backend is generated automatically to use the localstack endpoints for the remote state. This works in many cases, however if the desired backend configuration has been customized beyond the default options/configuration applied inTF_S3_BACKEND_CONFIG
(https://github.com/localstack/terraform-local/blob/main/bin/tflocal#L45), those options/configurations are lost.For example, if the desired backend configuration has
force_path_style = true
, that configuration is lost whentflocal
is used.This is the initial backend configuration from the tf files.
this is the backend configuration generated by tflocal as an override.
The text was updated successfully, but these errors were encountered: