Track installed marketplace actions in tenant.yaml

[zakwalters]

Checklist

• I agree to the terms within the Auth0 Code of Conduct.

Describe the problem you'd like to have solved

Currently, if you're using marketplace Actions, including those owned by Auth0, you have to manually install and configure them before they can be referenced in a tenant.yaml for import.

Describe the ideal solution

Running a0deploy export would export the fact that I'm using marketplace actions, along with their configuration. Running a0deploy import with the right values against a new tenant would successfully import/install/configure those actions.

Alternatives and current workarounds

The current workaround is to manually install the marketplace actions. They also need to be updated manually if configuration changes.

Additional context

The current error message isn't very helpful:

2025-05-09T13:28:38.778Z - error: Problem running command import during stage processChanges when processing type triggers
2025-05-09T13:28:38.778Z - error: That action does not exist.

A quick improvement would be to make the error message more informative, e.g.:

2025-05-09T13:28:38.778Z - error: Problem running command import during stage processChanges when processing type triggers
2025-05-09T13:28:38.778Z - error: The action 'Domain Based Registration v1' does not exist - if it is a marketplace action, you will need to install it manually through the dashboard

[kushalshit27]

Hi, @zakwalters
Thanks for the feature request. We will evaluate how to incorporate it. 👍

[kushalshit27]

Hi, @zakwalters
We're moving this feature request to a GitHub discussion to encourage broader collaboration and input from the community.