[ENH] - Add --dry-run option to qhub installation

[viniciusdc]

Feature description

The Terraform Provision and Terraform Apply steps in the qhub deploy could be executed as a dry run, just like running the terraform plan command.

The dry run would refresh the state file (if present) and generate a deployment plan based on the provided qhub infrastructure but not apply the plan.

Value and/or benefit

The benefits of doing so would be:

• Generating the qhub full infrastructure model and exporting/importing it to proper locations if needed -- infra cost might be able to use this for better predictions
• CI testing, we could then mimic the installation process and run these (without deploying an instance) into different architectures, like Windows, Linux, and macOS. This would help cathing situations such as [ENH] - Add support for M1 Macs #1367
• We would also be able to inspect the outputted plan and compare it with a pre-defined test template to assert versions, providers, and config maps are all well-defined and present.

Anything else?

#93 initially proposed this

[trallard]

There is a dry-run flag now in the CLI, is this issue still relevant? it seems it is now not applicable cc @viniciusdc and @iameskild

see

nebari/nebari/cli/main.py

Line 231 in 784ab81

"--dry-run",

[iameskild]

Hi @trallard, the dry-run flag above is for the nebari render, I believe there is interest in adding a dry-run flag for nebari deploy / nebari destroy.

Here is another issue was recently opened requesting something very similar: #1538. As I outlined in that issue, this can be a bit tricky given that we are deploying Terraform in stages.

[trallard]

ok since the other issue has more information I am going to close this as a duplicate and carry on with the discussion there