Omni Gateway Config

Read and validate YAML configuration files in an Omni Gateway conf.d directory. Use when a gateway returns unexpected 4xx/5xx errors after a config change and the user suspects a misconfiguration; when a new PolicyBinding or ApiInstance was added and is silently not taking effect; when conf.d files were edited manually and the user wants to catch errors before restarting the gateway; or when omni-gateway-diagnose determines that conf.d is the likely root cause.

mulesoft Updated 15 repo stars

File contents

mulesoft/anypoint-dev-portal commit 15702c04b7

Frequently asked questions

npx get-skill add mulesoft/omni-gateway-config