[FEATURE] allow all configuration via command args (and not force env for some)

[nikolockenvitz]

What area do you want to see improved?

CLI commands

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

I want to get started with Terraform/BTP and am trying out this tool. To make it simple, I would like to have a single command to run the export (that I can reuse / share with colleagues / ...). Right now, I need to set several values via env first (e.g., global account). On Windows/cmd this is not persisted for the next session. While I could generally also concatenate setting the env and the command itself, it feels somewhat arbitrary to have certain values via env and others via CLI arg.

Describe the solution you would like

I see the value of setting some general settings via env. Therefore I would suggest to use command line arguments as an override and fall back to env if none provided.

Describe alternatives you have considered

No response

Additional context

No response

[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]

In general the data provided via environment variables is the one needed for authentication with the Terraform Provider for SAP BTP or Cloud Foundry. The explicit command line arguments are the one that fit to the commands and their expected result like exporting a subaccount.

Adding the authentication information as parameters would clutter the commands.

This is to some extent connected to #205 namely it would be good to have a login (and logout) command for the CLI as one would have for the Azure or AWS CLI and then reuse login. However due to the setup of the provider and the currently supported login flows this is not possible as of today. There might be improvements as mentioned in #205, but there is no timeline attached to this.

Hence, we decided not to work on the feature request for now.