W-23612601 Main Branch for Aug 6 EME release (MS2026-08-R1) - #519
Open
glenn-rodgers-sf wants to merge 154 commits into
Open
W-23612601 Main Branch for Aug 6 EME release (MS2026-08-R1)#519glenn-rodgers-sf wants to merge 154 commits into
glenn-rodgers-sf wants to merge 154 commits into
Conversation
Add six new experience topics for third-party API provider governance: - exp-governance-setup-third-party-providers.adoc: Connect to Provider wizard with connection setup, scanner auto-creation, API discovery, and Akamai correlation policy auto-application - exp-governance-govern-third-party-apis.adoc: End-to-end workflow for connecting providers, verifying discovered APIs, creating governance strategies with Gateway/Provider filter, monitoring conformance, and exporting reports - exp-governance-policy-library-apply.adoc: Policy Library wizard with policy categories (Universal, Access and Security, Performance and Cost, Data Privacy and Integrity, Compliance and Observability) and targeted/supplemental application workflow - exp-governance-create-profiles-gateway-provider-filter.adoc: Gateway/Provider filter for governance scope, with provider selection and All Runtimes option - exp-governance-monitor-cross-gateway-conformance.adoc: Cross-gateway conformance monitoring with provider/gateway column filtering and Read-Only policy status indicator - exp-governance-cross-gateway-policy-audit-export.adoc: CSV export for SOC 2 / GDPR compliance audits with full schema including Organization ID, API ID, Gateway/Provider, Applied policies, Policy Application Status, Conformance status, and Timestamp Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Add exp-governance-third-party-policy-drift.adoc to document policy drift detection and remediation for third-party API gateway instances (Kong, Apigee, AWS API Gateway, and Akamai). Content includes: - What policy drift is and common causes (manual gateway changes, credential issues, policy application failures) - How to detect drift via conformance dashboard with drift indicators (Missing Policy, Extra Policy, Configuration Mismatch) - Remediation workflow using Policy Library to apply or update policies - Updating scanner credentials to enable write access and programmatic policy application - Monitoring policy drift over time with CSV exports and trend analysis - Best practices to prevent drift (restrict gateway access, document governance-managed policies, use write-enabled credentials) This topic provides the linkable target for docs-api-governance-documentation repo's "Find Policy Drift on Third-Party API Instances" section. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Restructure the third-party provider governance topics so they match what ships in the code and the Jul 16 Policy Read GA scope: - Remove the policy-drift topic (not in code or PRD scope) - Comment out policy-write (Aug 13) content behind flags: Policy Library apply, read-only/credential-update flows, Policy Application Status - Fix conformance terminology (Conformant/Non-Conformant, not Compliant) - Flag the Gateway/Provider filter topic for PM scope confirmation Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Neither the omni-app code nor the Jul 16 Policy Read PRD includes an "Export to CSV" feature for governance strategies or conformance data. The PRD's "conformance report" is an on-screen evaluation, not a downloadable artifact. - Delete the standalone Export Cross-Gateway Policy Audit Reports topic - Remove the Export Reports step and Export Cross-Gateway Reports section from the govern topic, plus the dangling xref - Remove the Export Conformance Reports section from the monitor topic, plus the dangling xref Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The "Gateway/Provider filter" as a strategy-scoping control isn't in the code, and the Jul 16 PRD strikes through source_gateway (provider-level scoping), scoping strategies by environment and applied_at_level instead. The literal label "Gateway/Provider" doesn't exist in the product; the real labels are "Provider" (column) and the provider view filter. - Delete the gateway/provider filter topic and its xrefs - Remove strategy-scoping-by-provider prose from the govern and monitor topics (including the incorrect "All Runtimes = all providers" claim) - Relabel the real conformance-view column and filter to "Provider" Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…and read policy creds
- "Portfolio Overview" is a Home-page summary section, not a destination; discovered APIs with the Provider column live under Portfolio > APIs. Correct the three navigation references. - Unbold the descriptive workflow step labels in the govern topic (they aren't UI elements) and trim the duplicated conformance-monitoring section that overlapped the dedicated monitor topic. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
The Provider column only appears in the Portfolio > APIs list (table) view; card view shows a provider badge and the API detail header shows a labeled Provider field. Describe the provider as a label rather than a column so the verification step is accurate across views. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
- Selecting a strategy opens the Configuration tab; conformance results live in the Governed Services tab. Correct the steps and describe the real Conformance / Identified Issues summaries and table columns. - Remove the "Monitor Conformance Over Time" section: no Conformance History chart or conformance-over-time trend exists in the product (conformance is a point-in-time snapshot with a last-evaluated time and a Refresh action). It is not in Jul 16 or Aug 13 scope. - Name the provider filter by its real resting label (Any provider); fix remaining "compliance" wording to "conformance." Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…gory) The Policy Library has four categories (Access and Security, Performance and Cost, Data Privacy and Integrity, Compliance and Observability). "Universal" is not a fifth category — it's a badge marking policies that apply to any service, including scanned and federated APIs. Correct the category list in the commented-out Aug 13 content in both topics so it's accurate when uncommented. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Retitle "Apply Policies via Policy Library" to "Browse the Policy Library" and add an uncommented read/browse introduction describing what the Policy Library is and what users can see (policy cards, search, the four categories, and the Universal badge). The browse intro is gated behind a "Jul 16 publish condition" note pending PM confirmation that the Policy Library feature flag is on in browse mode for Jul 16. The policy-application wizard remains commented behind the Aug 13 write flag, to be folded into the topic when that release is documented. Update the inbound xref label to match the new title. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…ding "What You Can See in the Policy Library" is a vague, question-like lead-in. Use "Browse Policies by Category" — a concise imperative that names what the section covers (search plus the four category filters) and matches the topic title. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
MuleSoft docs use "See Also" for the cross-reference section. Rename the "Related Topics" headings in the setup and monitor topics to match. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Scanner Auto-Creation, API Discovery, and Akamai Correlation Policy are descriptive category lead-ins, not UI element labels, so they shouldn't be bold. Rewrite the connection-results list as plain sentences. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Add the four PR 499 topics under Work with Governance Strategies in workflow order: connect providers, govern third-party APIs, monitor cross-gateway conformance, and browse the Policy Library. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
…arty-provider-governance-topics
…-governance-topics W-23392787 docs: add third-party provider governance experience topics
Co-authored-by: Hanna Nelson <johanna.nelson@salesforce.com>
- Fix bullet list inconsistency in prerequisites
- Remove punctuation from UI element references per style guide
- Fix inconsistent colon usage in examples
- Remove parentheticals from section headings
- Change "is designed for" to "supports" for more direct language
- Remove self-referential language ("this guide")
- Remove duplicate/leftover content sections
- Fix numbered list nesting issue
- Capitalize "Model Proxy" consistently in UI references
- Move MCP initialism expansion to heading
Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Keep the technical details (API endpoints, methods) in headings but remove the parentheses wrapping them per style guide. Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
Address PR review comments for Model Proxy documentation
W-23670545 update llm proxy gr
Start nav changes
…nner-api-read-policies-ga-jh
…-policies-ga-jh W-23435636 EME scanner read policy GA jh
Reconciling titles
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Rename "LLM Proxy" to "Model Proxy" for the Enhanced MuleSoft Experience docs in the
generalcomponent. These pages were moved here from thegatewaycomponent.File renames (git mv, history preserved)
llm-proxy.adoc→model-proxy.adocllm-proxy-create-llm-proxy.adoc→model-proxy-create-model-proxy.adocllm-proxy-policies.adoc→model-proxy-policies.adocllm-proxy-request.adoc→model-proxy-request.adocllm-proxy-semantic-service.adoc→model-proxy-semantic-service.adocllm-proxy-token-reports.adoc→model-proxy-token-reports.adocllm-proxy-try-out.adoc→model-proxy-try-out.adocContent replacements (case-preserving)
LLM Proxy/LLM Proxies/LLM proxy→Model Proxy/Model Proxies/Model proxythroughout the pages above plususage-metrics.adocandexp-services-add-to-portfolio.adoc.an Model Proxy→a Model Proxy).Reference updates
nav.adocentries updated to themodel-proxy*filenames.[[create-a-model-proxy]]and<<create-a-model-proxy>>).model-proxy*.adoc.Not changed
page-aliases(gateway::llm-proxy*.adoc,gateway::flex-gateway-llm-proxy*.adoc) preserved for redirects.