Terraspace documentation regarding terraspace "env variable"?

[tung]

Related PRs:

• add backend config variables docs comment by tongueroo · Pull Request #22 · boltops-tools/terraspace_plugin_aws · GitHub
• add backend config variables docs comment by tongueroo · Pull Request #18 · boltops-tools/terraspace_plugin_azurerm · GitHub
• add backend config variables docs comment by tongueroo · Pull Request #15 · boltops-tools/terraspace_plugin_google · GitHub

RE: we cannot add dynamically (multiple) new ones or can only use the :EXTRA one for the whole project?

Believe a boot hook can help with that. Take a look at Boot Hooks - Terraspace

With the boot hook, you can run any arbitrary logic you need early on. This includes setting one more multiple environment variables. You can key off of one env var, and based off of that set additional variables dynamically if you wish.

Also, other users have done some interesting things with the boot hook

Customized layering support?

Prior to seeing your response, I came up with a solution, or at least a way forward that works for now to continue with a POC – It’s to call the AWS Secure Token Service from within the terraspace boot hook to extract some temporary creds. I can then set those in the environment for use during the terraspace config phase. Code looks something like this (pardon my ruby…): # config/boot.rb require 'aws-sdk-sts' require 'json' # dynamically build up a role to assume and assume it # for the terr…