Config Authoring

adobe/skills/plugins/aem/cloud-service/skills/dispatcher/config-authoring

by adobe940b8795c0df3e25de68ce3881dc90855129b215Apache-2.0197 starsListed Oct 9, 2026Updated Oct 9, 2026Repository updated today

Create, modify, review, and harden configuration for the Adobe Dispatcher Apache HTTP Server module and Apache HTTPD in AEM as a Cloud Service environments only. Use for `.any`, vhost, rewrite, cache, and filter changes.

Instructions onlyDevOps & Cloud
AI-generated overview

Authors, reviews and hardens Adobe Dispatcher and Apache HTTPD configuration for AEM as a Cloud Service.

What it does
Guides an agent through designing minimal, deterministic Dispatcher and HTTPD configuration changes for AEM as a Cloud Service, covering .any files, vhosts, rewrites, caching and filters. It enforces cloud guardrails, decomposes target URLs, and runs static and SDK checks through a fixed set of Dispatcher MCP tools. It produces a diff, an evidence table, a risk and rollback plan, and documentation citations.
When to use it
Use when creating, modifying, reviewing or hardening Dispatcher or Apache HTTPD configuration in AEM as a Cloud Service environments. It fits changes to .any files, vhosts, rewrite rules, cache rules and filters that need verification evidence.
Requirements
Requires a Dispatcher MCP server configured for the cloud variant with AEM_DEPLOYMENT_MODE=cloud, and the tools validate, lint, sdk, trace_request, inspect_cache, monitor_metrics and tail_logs. Runtime verification needs a container-backed environment. Ships no scripts; instructions and reference documents only.

Dispatcher Config Authoring (Cloud)

Design minimal, deterministic changes for the Adobe Dispatcher Apache HTTP Server module and related HTTPD configuration in AEMaaCS, then verify with MCP evidence.

Variant Scope

  • This skill is cloud-service-only.
  • Scope is fixed by this skill directory; do not ask the user to choose deployment variant.

MCP Tool Contract

Use only these Dispatcher MCP tools:

  • validate
  • lint
  • sdk
  • trace_request
  • inspect_cache
  • monitor_metrics
  • tail_logs

Workflow

text
Cloud Config Progress- [ ] 1) Confirm scope and acceptance criteria; if the repo layout is unclear, normalize it with `repo-layout-workflows.md`- [ ] 2) Apply cloud guardrails (immutable files, required includes, symlink topology, required wildcard ServerAlias coverage, reserved probe paths, preserved cloud vhost defaults, CDN-vs-Dispatcher boundary)- [ ] 3) Decompose target URLs (path/selectors/extension/suffix) and use that model for all URL-based rules—filters, cache rules, etc.—using `/path`, `/selectors`, `/extension`, `/suffix` or aligned globs (not raw `/url`) where applicable; then design complete section-level edits- [ ] 4) Update config with least-privilege defaults (produce final merged section, not isolated rule snippets)- [ ] 5) Run static checks: validate -> lint (deep/order-aware when filters changed)- [ ] 6) Run SDK checks: `sdk({"action":"check-files","config_path":"<dispatcher src path>"})`, `sdk({"action":"diff-baseline","config_path":"<dispatcher src path>"})` as needed- [ ] 7) Run runtime verification in container-backed environment- [ ] 8) Return diff, evidence table, risk/rollback, and citations

Verification Scope Selection

Use the shared references to select the minimum evidence set:

  • mode-specific-verification-matrix.md
  • test-case-catalog.md

Output Contract

Always include:

  • files changed + intent
  • exact insertion location and final merged section content for each edited block
  • checks executed + evidence
  • selected test IDs
  • risk/rollback plan
  • residual risks and next checks

Feature cross-boundary (Playbook G)

Permission-sensitive caching (/auth_checker) is end-to-end: it requires both Dispatcher config and an AEM servlet. When implementing Playbook G from scratch, create or verify the auth-check servlet in the project core bundle (path /bin/permissioncheck, HEAD/GET, 200 or 403) and allowlist it on publish; then add the /auth_checker block, filter allow for the endpoint, and /allowAuthorized "1" in /cache. See config-scenario-playbooks.md Playbook G and reference-snippets.md.

Guardrails

  • Do not weaken deny-by-default security posture without explicit user approval.
  • Do not claim runtime verification if container/runtime prerequisites were missing.
  • Keep changes minimal and scoped.
  • Enforce cloud guardrails from cloud-service-aemaacs-guardrails.md before proposing config edits.

References

  • config-patterns.md
  • config-scenario-playbooks.md – high-value development scenarios adapted from broader MCP surfaces to core-7 execution
  • reference-snippets.md – reusable starter snippets for consistent config authoring
  • validation-playbook.md
  • mcp-tool-orchestration.md
  • For runtime prompts and troubleshooting scenarios (tail_logs, trace_request, monitor_metrics, inspect_cache), use the incident-response skill reference runtime-prompts-and-troubleshooting-scenarios.md when incident triage is needed.
  • quick-start-execution-path.md – single entry path for new users and broad requests
  • local-sdk-execution.md – shipped local SDK launcher contract for docker_run.sh, hot reload, and runtime env vars
  • repo-layout-workflows.md – map the user repo to the dispatcher src root and likely file families
  • playbook-command-linkage.md – convert selected playbooks into exact MCP command chains
  • mode-specific-verification-matrix.md
  • cloud-service-aemaacs-guardrails.md – cloud-service-only immutable/include/runtime boundary checks from AEMaaCS patterns
  • test-case-catalog.md
  • change-risk-and-rollback-template.md
  • public-doc-citation-rules.md
  • public-docs-index.md
  • core-7-tools-reference.md

Source and attribution

Source:adobe/skillsinplugins/aem/cloud-service/skills/dispatcher/config-authoringat commit940b879

License: Apache-2.0

Content belongs to its original authors. SourceWeft indexes it from a public repository.

Report or request removal