[FEATURE] Injection of parameters for export

[lechnerc77]

What area do you want to see improved?

other

Is your feature request related to a problem? Please describe.

When importing multiple subaccounts and/orgs and executing the setup of these imports it is cumbersome to add the different subaccount_ids/org_ids to the CLI .

While the authentication data can be provided via .env files this information must be explicitly keyed in.

Describe the solution you would like

It would be good if one could define the information centrally maybe even be leveraging the variables.tf and terraform.tfvars mechanics to inject the information besides the authentication information.

This would then also enable the reuse of the variables when applying the terraform configurations.

Describe alternatives you have considered

n/a

Additional context

n/a

[github-actions]

Thanks for the feature request. We evaluate it and update the issue accordingly.

Community Note

Voting for Prioritization

• Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
• Please do not leave "+1" or other comments that do not add relevant new information or questions, they generate extra noise for issue followers and do not help prioritize the request.

Volunteering to Work on This Issue

• If you are interested in working on this issue, please leave a comment.
• If this would be your first contribution, please review the contribution guide.

[lechnerc77]

Injecting the variables from *.tfvar files is not straightforward with respect to the setup of the exporter as of now.
The terraform plan and terraform apply commands executed when the export is triggered assume that the are set via environment variables.
Reading the variables from the files namely parsing the *.tfvar files is not complicated. However, injecting the values in the processing (data source creation, import geeneration) is more complicated:

• Setting them implicitly as env variables would be the easiest approach, but would jeopardize the idea of the request. It can also have side effects on the setup of the user.
• Writing the values to the provider.tf file as attributes of the configuration is a security issue as the password would be available in plain text
• Adding the values consistently would mean to add a variables.tf file with the parameters marked as sensitive or ephemeral depending on the availability of feature in Terraform/OpenTofu and then creating a terraform.tfvars file with the desired content from a file provided by the user. Here we might run into conflicts with naming conventions of customers putting this information into a e.g., secrets.tfvars file. This could be mitigated by adding parameters to the CLI which comes at the price that the CLI command gets messy.