Config Authoring

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

作者 adobe940b8795c0df3e25de68ce3881dc90855129b215Apache-2.0197 个星标收录于 2026年10月9日更新于 2026年10月9日仓库今天更新

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.

仅含说明DevOps & Cloud
AI 生成的概览

为 AEM as a Cloud Service 编写、审查并加固 Adobe Dispatcher 与 Apache HTTPD 配置。

功能
引导智能体为 AEM as a Cloud Service 设计最小化且确定性的 Dispatcher 与 HTTPD 配置变更,涵盖 .any 文件、虚拟主机、重写、缓存和过滤器。它会执行云端护栏检查、拆解目标 URL,并通过一组固定的 Dispatcher MCP 工具运行静态与 SDK 检查。产出包括差异、证据表、风险与回滚方案以及文档引用。
适用场景
适用于在 AEM as a Cloud Service 环境中创建、修改、审查或加固 Dispatcher 与 Apache HTTPD 配置。适合需要验证证据的 .any 文件、虚拟主机、重写规则、缓存规则和过滤器变更。
运行要求
需要配置为云端变体的 Dispatcher MCP 服务器,并设置 AEM_DEPLOYMENT_MODE=cloud,以及 validate、lint、sdk、trace_request、inspect_cache、monitor_metrics 和 tail_logs 工具。运行时验证需要容器化环境。不附带脚本,仅包含指令与参考文档。

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

来源与署名

来源:adobe/skills位于plugins/aem/cloud-service/skills/dispatcher/config-authoring提交940b879

许可证: Apache-2.0

内容归原作者所有。SourceWeft 从公开仓库中收录这些内容。

举报或申请下架