Make CI-created scratch orgs more usable by downstream webhooks
If a CI job creates a scratch org ; and you configure an outgoing webhook in the CI configuration, the subscribers to that webhook have no way of being able to connect/authenticate to that scratch org.
The typical use case would be to run automated UX testing (Provar, Selenium)
At present, even the CI job creator can't log into the CI-created scratch org let alone any CI webhook
In addition to supporting this, there should be doc on how a downstream webhook can access the scratch org to then do useful work.
Eric Kintzer
shared this idea
-
A solution would be to provide two dynamic params in the outgoing webhook JSON payload:
username (of the newly-created scratch org)
JWT (to the dev hub)see http://www.wadewegner.com/2018/01/jwt-oauth-with-scratch-orgs/
this allows remote machines to login to the scratch org with only a username