Managed to get some answers:
1. Is there an estimate on how long they can rely on the deployment extension working?
Unfortunately as of now there is no information about that.
2. Is there a migration path for them to continue deploying via version control and CI/CD? Is it to use the deploy-cli directly?
You should switch to the integrations that is linked in the changelog entry (It’s titled “Changed: Changes to our Deploy Extensions” on 2021-02-25), the integration and an install guide. Using the deploy-cli directly is also an option.
Here’s the full changelog item:
Starting today, we are replacing our deploy extensions with improved solutions for a better CI/CD experience. Deploy extensions were built at a time before automated code deployment services from web-based DevOps tools. With the advent of Gitlab Pipelines, Github Actions, Bitbucket Pipelines, and Azure Pipelines, the extensions we previously provided are now obsolete in a world of direct CI/CD solutions provided by the SaaS partners directly. The following Extensions will no longer be available in the extension gallery.
- Auth0 Deploy CLI Extension
- Visual Studio Team Services Deployments
The services and solutions provided by these extensions will continue to work for developers who have previously configured the extensions. For developers looking to employ the functionality previously provided through these extensions, we have created a series of guides available in the Auth0 Marketplace that provide a more custom and improved experience than the extensions provided.
- GitLab Pipelines
- Github Actions
- Bitbucket Pipelines
- Microsoft Azure Pipelines
With the Deploy CLI Extension, we received feedback from many customers that as our product evolved the extension provided additional friction to enabling Deploy CLI. The Deploy Extension was intended to be a quick solution to creating an application in your dashboard to quickly connect your external Deploy CLI with your Auth0 instance, however, as the Deploy CLI evolved, so did the need for more customization in how the service connected. The functionality formerly found through the extension will now be served through the Deploy CLI installation guide.
3. Are there any customer-facing reasons that can be shared as to why these extensions were deprecated?
Unfortunately there is no public information on that front