Deploy CLI: Export tenant configuration Not Found error

Hello all,
I am trying to export a config of my configured Auth0 tenant running the commant: a0deploy export --config_file config.json --format yaml --output_folder ./
but during the export I’m getting Not Found error, the log is poor -

Does anyone have any ideas what could be the problem?

Hey there @art.bohush welcome to the community!

Can you confirm which version of auth0-deploy-cli you are using?

1 Like

Yes, sure. I’m using the following version -



1 Like

Sorry for the delayed response and thanks for confirming the vresion @art.bohush! Were you able to resolve this?

I just tested this against my own tenant with version 7.6 and the export was successful. Are you able to update to the latest version (7.6) and let me know if you experience the same issue? Additionally, did you use auth0-deploy-cli-extension to create the required application? If so, it might be worth updating that as well.

Let us know!

1 Like

@tyf Unfortunately I still cann’t export configs. I’ve updated deploy cli to 7.6.0 version

Regarding auth0-deploy-cli-extension, my tenant does not have the application with such name. I’m using the machine-to-machine application with “Auth0 Management” name that has all scopes enabled.

Btw, I am trying to export config from an enterprise tenant, not own. We already have pipeline to migrate configs from one tenant to another. But I cann’t export configs locally.

Hi, I would like to add to Art’s issue regarding export as well; I feel something has changed in the last 3 weeks.

I use Azure DevOps to backup my Auth0 tenant using the simple export command.
It ran successfully on 10/03/2022 but when I ran the same pipeline today 31/03/2022, it failed on the export

2022-03-31T06:41:13.0813479Z 2022-03-31-16h41m12s2022-03-31T06:41:13.078Z - e[34mdebuge[39m: Start command export
2022-03-31T06:41:13.0876976Z 2022-03-31T06:41:13.087Z - e[32minfoe[39m: Creating auth0-export
2022-03-31T06:41:13.2090373Z 2022-03-31T06:41:13.208Z - e[31merrore[39m: Problem running command export
2022-03-31T06:41:13.2091344Z 2022-03-31T06:41:13.208Z - e[31merrore[39m: getaddrinfo EAI_AGAIN null
2022-03-31T06:41:13.2101535Z 2022-03-31T06:41:13.209Z - e[34mdebuge[39m: APIError: getaddrinfo EAI_AGAIN null
2022-03-31T06:41:13.2102827Z     at /opt/hostedtoolcache/node/17.7.0/x64/lib/node_modules/auth0-deploy-cli/node_modules/rest-facade/src/Client.js:402:25
2022-03-31T06:41:13.2104152Z     at Request.callback (/opt/hostedtoolcache/node/17.7.0/x64/lib/node_modules/auth0-deploy-cli/node_modules/superagent/lib/node/index.js:905:3)
2022-03-31T06:41:13.2105846Z     at ClientRequest.<anonymous> (/opt/hostedtoolcache/node/17.7.0/x64/lib/node_modules/auth0-deploy-cli/node_modules/superagent/lib/node/index.js:822:12)
2022-03-31T06:41:13.2106705Z     at ClientRequest.emit (node:events:527:28)
2022-03-31T06:41:13.2107310Z     at ClientRequest.emit (node:domain:475:12)
2022-03-31T06:41:13.2107925Z     at TLSSocket.socketErrorListener (node:_http_client:442:9)
2022-03-31T06:41:13.2108542Z     at TLSSocket.emit (node:events:527:28)
2022-03-31T06:41:13.2109104Z     at TLSSocket.emit (node:domain:475:12)
2022-03-31T06:41:13.2109674Z     at emitErrorNT (node:internal/streams/destroy:164:8)
2022-03-31T06:41:13.2110300Z     at emitErrorCloseNT (node:internal/streams/destroy:129:3)
2022-03-31T06:41:13.2262883Z   adding: auth0-export/ (stored 0%)

Hey @art.bohush and @sams - Sorry for the delayed response, but wanted to follow up here! I haven’t had any luck reproducing albeit just in my own testing environment Would you mind filing an issue against the repo itself? I just want to make sure this gets visibility with the maintainers and any one else who might be experiencing similar issues.


1 Like

@art.bohush - Sorry for hijacking your post. I too am running a0deploy 7.5.2 locally and I was able to perform an export.

Could you please add --debug to you export script?

a0deploy export --config_file config.json --format yaml --output_folder ./ --debug

@tyf - I logged a job with Microsoft and managed to resolve the issue.
Case 2203310030000769 TrackingID#2203310030000769

The root cause of my issue was a0deploy 7.6. It was resolved by forcing 7.5.0 to be installed

npm i -g auth0-deploy-cli@7.5.0
1 Like

This topic was automatically closed 15 days after the last reply. New replies are no longer allowed.