You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
JFYI, there are "indirect" ways to manage mapping rules. I can think about two ways:
Product export to yaml, then add/delete/update mapping rules in the yaml, product import from the yaml. The toolbox will ensure that 3scale configuration matches the one in the yaml doc.
Manage the mapping rules from the OpenAPI spec doc. Change your OAS operations (translated to 3scale mapping rules) and run 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:
#3scale mapping-rules list [opts] <remote> <service> 3scale -k mapping-rules create remote 2 --metric-id=6 --http-method=GET --pattern=/api 3scale -k mapping-rules list remote 2
Any ideas or if this is useful or not?
The text was updated successfully, but these errors were encountered: