Speed creation of auth0 & mapbox keys, and auto-inject them into a new stack.yaml for deployment

[IamJeffG]

Feature Request

https://github.com/ConservationMetrics/gc-forge/issues/104#issuecomment-5036356206 shows that 30% of our time in a new deployment is in these three steps:

• configuring auth0 (new tenant, new application clients for each of {superset, explorer, etc})
• set up GCP OAuth client for Google social login
• configuring mapbox (provisioning an access key -- right @rudokemper ?)
• populating stack.yaml -- largely with the credentials produced by the previous two bullets

This flow seems ripe for automation.

• auth0 clients can be created via terraform (we actually used to do this before!) or API calls.
• The initial stack.yaml template is already output from a script (gc-stack-deploy init), it's plausible to imagine seeding that with some simple output from the auth0 & mapbox steps.

User Stories & Acceptance Criteria

UI Sketch

One idea: A very hands-off wizard (script or app) that
inputs

• only your admin auth0 login (or better, an M2M client credential)
• TODO: GCP, mapbox ... something..?
• lets you confirm which app clients you need created

effects

• it creates the application tenants,
• it creates the mapbox key(s),
• and spits out your stack.yaml with those values populated.

If this is run on the target VM, then a very good feature would be to require only one installer, that provides the user both this and gc-stack-deploy, i.e. the user only has to install one thing!

Implementation Plan

How should the wizard interact with auth0?

• The vibe-coder would probably use their JS or Python API.
• Or, could the installer install terraform (or OpenTofu) on the VM itself, deploy using Terraform (which we have code for already), and possibly even delete itself later (long-term maintenance is not the use case)

Bonus (scope-creep)

You could also automate generating the SECRET_KEY(s)
... and even writing them to Keepass.

The issue title frames it as automating auth0, mapbox setup; I wonder if a more useful & intuitive framing might be "make a full-featured stack.yaml generator".

[rudokemper]

Agree with this in principle. My only caveat is that 4:26 minutes of Mapbox largely involves things that seem hard to automate, at least steps 1-3 here:

1. Create a new account (we create gc+<alias> accounts for every user)
2. Fill out the required forms like address
3. Wait for a confirmation email, and click through
4. Then when you log in you can copy a Mapbox access token to put into KeePass
5. Next, generate a secret token with the right scope, and add that to KeePass

But I agree on automating auth0 and maybe GCP, and seeding stack.yaml as much as possible.

auth0 is by far what takes the most amount of manual clicks and entry for the same things every time. (Scaffolding Windmill with the right resources etc. takes second place.)

[IamJeffG]

Great. For Mapbox, maybe there's just 1 page of the wizard that lists the Mapbox steps and has you come back once you have the tokens. Or even more likely, maybe we'd just leave Mapbox out of the first version of this.