remote-desktop module should complete the setup process on behalf of the user about hpc-toolkit HOT 4 CLOSED

Looking at the chrome inspector during https://remotedesktop.google.com/ setup, it seems the following scopes could are negociated, thru a regular oauth 2.0 server flow:

• https://www.googleapis.com/auth/chromoting.directory
• https://www.googleapis.com/auth/userinfo.email

But according to https://groups.google.com/a/chromium.org/g/chromium-dev/c/v9BNawrY-Xk/m/fx9y00QJAgAJ and https://groups.google.com/a/chromium.org/g/chromium-dev/c/v9BNawrY-Xk/m/fx9y00QJAgAJ, I'm unclear if it would be possible to rebuild the chromoting host tooling against a different client-id/client-secret provisionned during deployment.

from hpc-toolkit.

Alternatively we could ask the user to perform the step ahead of the deployment, and pass the resulting code= parameter showing up in the chromoting setup command snippet as a var of the terraform recipe.

from hpc-toolkit.

/cc @nick-stroud

from hpc-toolkit.

@cboneti mentioned that we could use https://github.com/GoogleCloudPlatform/hpc-toolkit/blob/main/community/modules/remote-desktop/chrome-remote-desktop/README.md#input_startup_script for this, but that we also need to set or generate the pin.

from hpc-toolkit.