Closed IceBear2k closed 2 years ago
I have further analyzed this issue and it turns out it's not the expansion that's not working, it's the loading of the Scaleway plugin entirely.
https://github.com/boltops-tools/terraspace/pull/195 has changed how Terraspace autodetects plugins, especially option number 2 is relevant here:
backend.tf parsing - will try to find the s3, azurerm, gcs backend and use the right terraspace plugin based on that.
Since Scaleway also uses S3 as a backend, Terraspace believes it has successfully identified usage of the AWS plugin, resulting in the above error messages.
To fix this, and make the Scaleway plugin usable with any Terraspace version >= 0.7.0 (including 1.x), simply add the following to the project's config/terraform/app.rb
:
Terraspace.configure do |config|
config.autodetect.expander = "scaleway"
end
This will overwrite the autodetection (mentioned as option number 1 in the PR above).
Might be worth noting in the plugin's documentation.
Terraspace has changed expansion lookups with the release of 0.7.0.
Lookups for
:REGION
or:ZONE
don't seem to be correctly delegated to the Scaleway plugin anymore. The following setup works correctly with 0.6.x: