kubefirst terraform command should throw error when not able to connect to Vault

[fharper]

Which version of kubefirst are you using?

2.6.1

Which cloud provider?

None specific

Which DNS?

None specific

Which installation type?

None specific

Which distributed Git provider?

None specific

Did you use a fork of gitops-template?

No

Which Operating System?

None specific

What is the issue?

If the command kubefirst terraform set-env isn't able to connect to Vault (example, someone pasted the --vault-token with a % at the end which isn't valid (not sure if happen only in this case on in all bad token cases), the command run without any error, but obviously won't work, and generate the .env file it is supposed to do. The command should return an error in that case.

Code of Conduct

• I agree to follow this project's Code of Conduct

[linear]

KON-35 kubefirst terraform command should throw error when not able to connect to Vault

[fharper]

@konstructcarrie FYI, the issue you had last week.