Separate repositories for pushing configuration changes

Help
1

I want to create two separate GitHub repositories for my organization: auth0-pages and auth0-emails. They will be managed by two separate teams with dramatically different workflows.

We have a version of auth0-pages that deploys with the GitHub Deployments extension, but we’d prefer a workflow where we push changes to Auth0’s servers, instead of letting the GitHub Deployments extension pull from a branch. It makes our build tooling much simpler.

  • With the Auth0 Deploy CLI, can we push only pages changes from auth0-pages and only emails changes from auth0-emails? We don’t want to have to touch any of the rest of the tenant’s configuration.
  • If the Auth0 Deploy CLI can’t do that isolation, can the Auth0 Management API?
3

Hi @cherewaty! Welcome to the Auth0 community.

If you’d like to keep these changes isolated, you can use the Management API.

The Password Reset, Multi-factor Authentication, and Custom Error Page can be updated using the Update tenant settings endpoint with the following objects:

{
  "change_password": {
    "enabled": true,
    "html": "<html of page>"
  },
  "guardian_mfa_page": {
    "enabled": true,
    "html": "<html of page>"
  },
  "error_page": {
    "url": "<url of page>"
  }
}

The Login page is different as it’s exposed via the Client endpoint rather than the Tenant endpoint. However, you can update all your clients by providing your Global Client ID to the Update a client endpoint with the following objects:

{
  "custom_login_page_on": true,
  "custom_login_page": "<html of page>"
}

Note: Remember to JSON.stringify() your HTML before passing it to the API.

2 Likes