ManagementApi does not include a client for Rules Configs

[caldwell0414]

Describe the problem you'd like to have solved

We make use of the ManangementApi to automate configuration of our tenants. This includes managing rules. We are unable to set config variables because there is no client in the API to call the /rules-configs endpoints on the Auth0 v2 management API.

Describe the ideal solution

We will provide a PR that implements a RulesConfigClient that follows the pattern of other clients and includes the cleanup work done by @frederikprijck in the chore/test-cleanup branch. We recommend that you accept his PR prior to accepting ours.

We appreciate the opportunity to contribute to this library.

Alternatives and current work-arounds

The only current work around is to use an HTTP client and make direct PUT and DELETE requests to the v2 Management API endpoints.

Additional information, if any

For security reasons, rules configuration variables cannot be read from the API, so there is no GET implementation in our PR. We confirm through unit tests that the CreateOrUpdateAsync() calls will either create or overwrite existing configuration variables.

Finally, it is important to note that the default scopes generated for the Management API client do not include rules-configs:delete, so customers will have to add this scope in order to use the DeleteAsync() method call. We confirmed that the API correctly returns the 403, along with a message indicating the missing scope when it is not present.

[frederikprijck]

Will be included in the next release, thanks for the PR!

[caldwell0414]

You are very welcome. I apologize for being away this week and unable to make the changes you requested. I appreciate your help in getting this PR merged! jc From: Frederik Prijck ***@***.***> Sent: Friday, March 4, 2022 6:35 AM To: auth0/auth0.net ***@***.***> Cc: James Caldwell ***@***.***>; Author ***@***.***> Subject: Re: [auth0/auth0.net] ManagementApi does not include a client for Rules Configs (Issue #551) Will be included in the next release, thanks for the PR! — Reply to this email directly, view it on GitHub<#551 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/ATA3OEQJK5Q4VESKQ4I33SDU6HYNXANCNFSM5PH4XGHQ>. You are receiving this because you authored the thread.Message ID: ***@***.***>