Open r-lam opened 2 years ago
I think it might be useful.
JFYI, there are "indirect" ways to manage mapping rules. I can think about two ways:
3scale import openapi
. The toolbox will ensure that 3scale configuration matches the one in the OAS doc.
The toolbox can update proxy related configuration but, limited to proxy endpoint on API, it can't access proxy mapping rules endpoints since there's no command for it.
My use case is a client requirement for translate this process to CI/CD environment with scripts and is getting complex to do with API requests only.
I've already take hands on it: fork the project and start the journey with ruby. So far, manage to code list, create subcommands like:
Any ideas or if this is useful or not?