Error deploying ruleconfig in directory mode

Description

As of v7.7.0 released earlier today, attempting to deploy ruleconfig assets fails with an error. This issue was not present in 7.6.0.

Reproduction

1. Create a directory mode setup with ruleconfig assets defined
2. Deploy
3. Observe error:

2022-04-06T17:55:25.326Z - debug: Start command deploy
2022-04-06T17:55:25.655Z - info: Processing directory .
2022-04-06T17:55:26.770Z - debug: Start processChanges for rulesConfigs [delete:0] [update:2], [create:0], [conflicts:0]
2022-04-06T17:55:26.771Z - error: Problem running command deploy during stage processChanges when processing type rulesConfigs
2022-04-06T17:55:26.772Z - error: Cannot read property 'bind' of undefined
2022-04-06T17:55:26.772Z - debug: TypeError: Cannot read property 'bind' of undefined
    at RulesConfigsHandler.getClientFN (<redacted>/.config/yarn/global/node_modules/auth0-deploy-cli/lib/tools/auth0/handlers/default.js:45:31)
    at Proxy.generator (<redacted>/.config/yarn/global/node_modules/auth0-deploy-cli/lib/tools/auth0/handlers/default.js:200:43)
    at Proxy.generator (<redacted>/.config/yarn/global/node_modules/promise-pool-executor/public/pool.js:200:42)
    at Proxy._run (<redacted>/.config/yarn/global/node_modules/promise-pool-executor/private/task.js:212:39)
    at Proxy._triggerNow (<redacted>/.config/yarn/global/node_modules/promise-pool-executor/public/pool.js:267:22)
    at Proxy.addGenericTask (<redacted>/.config/yarn/global/node_modules/promise-pool-executor/public/pool.js:102:14)
    at Proxy.addEachTask (<redacted>/.config/yarn/global/node_modules/promise-pool-executor/public/pool.js:186:21)
    at RulesConfigsHandler.<anonymous> (<redacted>/.config/yarn/global/node_modules/auth0-deploy-cli/lib/tools/auth0/handlers/default.js:197:18)
    at Generator.next (<anonymous>)
    at fulfilled (<redacted>/.config/yarn/global/node_modules/auth0-deploy-cli/lib/tools/auth0/handlers/default.js:5:58)

Environment

• auth0-deploy-cli: v7.7.0
• node: lts/fermium (v14.18.2)
• OS: macOS 12.3.1

[willvedd]

Just released a fix for this with a v7.7.1 release. My explanation in #482:

This is indicative of a “missing” method for the rules config asset type in the Node SDK.

The Deploy CLI relies upon a dynamically generated mapping between the assets managed and the Node Auth0 library. In general, each asset type has a correlating manager in that library including the update, delete, create and getAllmethods. However, for a select few asset types, the method names are different (ex: rules configs uses set instead of update). This requires the option to override these mappings on a per-asset basis. In this specific case, the override that the rules configs asset type uses to declare this override can be seen here.

During the Typescript migration, it wasn’t clear why this dynamic scheme was being used. I had mistakenly interpreted as an unnecessary abstraction and decided to deleted in favor of more hardcoded function names. In fact, during this refactor, I had incurred a suddenly-failing rules configs test, a warning I should have heeded in hindsight.

Apologies for the inconvenience and thanks for the patience!

[GrzegorzKozub]

Same problem for us since 7.7.0. Worked fine in 7.6.0.