Incorrect path delimiter used when exporting actions on Windows

Description

When exporting a tenant with a action on Windows, the JSON metadata uses the Windows path delimiter (\) within the “code” field. This is fine if you then re-run the import on Windows again, however, for teams that use multiple OSs (and also CI/CD pipelines running Linux) this becomes a problem as the following error is displayed when running the import:

error: Unable to load file /opt/atlassian/pipelines/agent/build/auth0\actions\action-name\code.js due to Error: ENOENT: no such file or directory, access '/opt/atlassian/pipelines/agent/build/auth0\actions\action-name\code.js'

Example of json file

{
  "name": "action-name",
  "code": "auth0/actions/action-name/code.js",
  "runtime": "node16",
  "status": "built",
  "dependencies": [],
  "supported_triggers": [
    {
      "id": "credentials-exchange",
      "version": "v2"
    }
  ],
  "deployed": true
}

Reproduction

• Create a tenant with an action
• Export the tenant using a0deploy on a Windows OS
• Import the tenant using a0deploy on a none Windows OS

Environment

Please provide the following:

• Version of this library used: 7.2.0
• Version of the platform or framework used, if applicable: Windows/Ubuntu Linux

[willvedd]

Update: After investigation it has been determined that this issue is only scoped to actions and when the operating systems of the machines that performed the import differs from that of the machine that did the export. Meaning, this issue won’t be experience if a windows machine performs both the export and the import.

The fix has been released with 7.15.1. It converts the path at runtime to support both windows and unix machines. Doing so maintains backwards-compatibility and won’t necessitate a new export of your actions.

Otherwise, we don’t have reason to believe that any other Windows issues exist at this time. If anyone is still having issues after updating, please feel empowered to open a new ticket.

[sergiught]

Hey folks, we fixed this in https://github.com/auth0/auth0-deploy-cli/pull/668 and it will be available in the next release. Appreciate everyone’s patience!