Make Auth rerun

[West-P]

Description

In my Azure TRE deployment I am trying to run make letsencrypt. The TRE is already in use and operational. I am on a new virtual machine that has never run make auth which will be required before I run make letsencrypt.
If I run make auth, will the currently deploy service principals have their secrets renewed by running this? Or does the make auth script check for existing secrets and pull them if they are still valid?

Is there a way of reestablishing the devcontainer cached config without renewing secrets?

[marrobi]

If you have the original config.yaml, that is the happy path. In normal use, config.yaml is the source of truth for the app IDs/secrets that get used by the TRE, and deployment persists those values into Azure Key Vault. So on a new VM/devcontainer, the simplest approach is to restore the same config.yaml and continue from there.