Skip to content

feat(omni-gateway): add Flex Gateway skill bundle (v0.1.1)#129

Open
adcarabajal wants to merge 3 commits into
mulesoft:masterfrom
adcarabajal:adcarabajal/flex-skills
Open

feat(omni-gateway): add Flex Gateway skill bundle (v0.1.1)#129
adcarabajal wants to merge 3 commits into
mulesoft:masterfrom
adcarabajal:adcarabajal/flex-skills

Conversation

@adcarabajal

Copy link
Copy Markdown

Introduces a complete skill bundle for Anypoint Flex Gateway operators, covering the full lifecycle from installation to diagnosis.

Skills included:

  • validate-gateway-config: validate gateway resource YAML files against real resource kinds (PolicyBinding, Service, TlsContext, etc.) with structural and cross-reference checks
  • install-omni-gateway: step-by-step install on Linux, Docker, and Kubernetes
  • register-gateway: register a gateway instance with Anypoint Control Plane
  • inspect-gateway-logs: query and interpret gateway logs (Docker / Kubernetes)
  • analyze-gateway-dump: parse and summarise diagnostic dumps
  • diagnose-gateway-error: triage runtime errors using conf.d and log context

Also adds skills-metadata.yaml, package.json, and CHANGELOG.md to the bundle.

Introduces a complete skill bundle for Anypoint Flex Gateway operators,
covering the full lifecycle from installation to diagnosis.

Skills included:
- validate-gateway-config: validate gateway resource YAML files against real
  resource kinds (PolicyBinding, Service, TlsContext, etc.) with structural
  and cross-reference checks
- install-omni-gateway: step-by-step install on Linux, Docker, and Kubernetes
- register-gateway: register a gateway instance with Anypoint Control Plane
- inspect-gateway-logs: query and interpret gateway logs (Docker / Kubernetes)
- analyze-gateway-dump: parse and summarise diagnostic dumps
- diagnose-gateway-error: triage runtime errors using conf.d and log context

Also adds skills-metadata.yaml, package.json, and CHANGELOG.md to the bundle.
@adcarabajal adcarabajal requested a review from a team as a code owner June 9, 2026 19:29
@@ -0,0 +1,439 @@
---

## name: install-omni-gateway

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Name is required

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I also think that install and register should be just one skill

configuration files to complete the setup. For CloudHub 2.0 managed deployments,
use provision-managed-gateway instead.

# Install Omni Gateway

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I don't think this section is needed

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do you mean the whole installation skill or just the cloudhub installation?

@@ -0,0 +1,354 @@
---
name: validate-gateway-config

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

When some customer is going to use this skill?

Copy link
Copy Markdown
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The skill is triggered in four scenarios:

  1. After a config change causes unexpected errors. User suspects a YAML misconfiguration.
  2. Silent no-op resources — a new PolicyBinding or ApiInstance was added but is silently not taking effect (wrong apiVersion, orphaned targetRef, etc.).
  3. Pre-deploy sanity check — conf.d/ files were edited manually and the user wants to catch hard errors before restarting the gateway.
  4. Escalation from diagnose-gateway-error — that skill acts as a router and calls this one when it determines conf.d is the likely root cause.

In short: any time a customer touches their Flex Gateway YAML configuration and wants to know if it's correct before (or after) applying it.

Dario Carabajal and others added 2 commits June 11, 2026 11:04
Consolidate gateway setup into a single skill: registration steps and
parameter guidance are now part of install-omni-gateway. Removed the
standalone register-gateway skill and updated all cross-references in
diagnose-gateway-error, inspect-gateway-logs, and the bundle index.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants