W-21433121 agent network 2.0 content ie#660
Open
IsaacEldridge wants to merge 34 commits into
Open
Conversation
…nent Split the af-* pages into a new agent-network Antora component with 1.0 and 2.0 versions so 2.0 can evolve independently while 1.0 stays frozen. Add page-aliases on 2.0 to redirect existing anypoint-code-builder::af-* URLs to the latest version. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
…eferences. Update navigation to include new references and clarify deployment target requirements for CloudHub 2.0. Adjust language for consistency across documentation.
- Introduced a new page detailing the process of building an IT Investigation Broker using MuleSoft Vibes, including phases from input requirements to final topology review. - Updated navigation to include a reference to the new example page. - Added a new workflow diagram image for the IT Investigation Broker. - Updated the existing agent fabric architecture image.
…JSON formatting - Updated the navigation to correct the reference to the IT Investigation Broker example. - Reformatted the JSON structure in the af-example-it-investigation-broker.adoc for improved readability and clarity. - Organized the project structure section for better visual representation.
- Introduced new partial documentation for creating agent networks, including prerequisites, platform requirements, and task overviews. - Detailed steps for setting up agent networks, creating projects, defining specifications, publishing assets, and deploying instances. - Ensured consistency in language and structure across both versions to facilitate user understanding.
…nd default URLs for OpenAI and Gemini. Added references for better clarity and user guidance.
…`on_exit` property across various node types, specifying that if `on_exit` is not defined, the graph ends when the agentic node loop concludes, and that only `transition_to` statements are permitted in the procedure.
…delines for publishing project assets. Added a note on using version groups instead of semantic versions to prevent unintended major upgrades. Enhanced language for consistency and clarity in the publishing process using MuleSoft Vibes and Anypoint Code Builder.
…-reference.adoc, specifying that if `on_exit` is not defined, the graph ends when the agentic node or executor ends, rather than when the node loop concludes. This update enhances the accuracy of the documentation regarding node execution behavior.
… configurations. Changed specific mention of `broker1.agent` files to `.agent` files for clarity and consistency in documentation regarding multi-agent orchestration.
…ructions for project asset publishing. Clarified that Exchange automatically increments the version upon changes, enhancing the documentation's clarity and accuracy regarding version group usage.
…configuration instructions. Updated descriptions for using MuleSoft Vibes and Anypoint Code Builder, clarified file structures, and improved prompt examples for better user guidance. Added notes on utilizing the visual canvas alongside code editing for effective network management.
…, capabilities, and transport types. Updated sections on project creation, asset management, and deployment processes in Anypoint Code Builder for improved clarity and user guidance.
…ructure, replacing references from `/agent-script` to `/brokers` for improved clarity in navigating broker configurations.
…ference.adoc by specifying the use of authorization headers in OBO authentication scenarios, enhancing the understanding of custom header requirements for external system connections.
…Network version from a quoted string to a numeric value for improved clarity and consistency.
… instructions and correct A2A protocol version from 0.3.0 to 1.0.0, enhancing clarity and accuracy in troubleshooting guidance.
…on.adoc that was wrapping the rest of the page in an example block, causing all subsequent headings to render as literal AsciiDoc syntax.
…affic, and data by the Omni Gateway in shared and private space configurations.
…diagram. Update documentation to reflect changes in architecture and clarify Omni Gateway usage in shared and private space configurations.
…jects. Clarify the process for referencing assets from different business groups and provide a complete example of `exchange.json` and `agent-network.yaml` configurations to improve user understanding.
…exchange-dependencies-to-agent-network-file-ie W-22730742 example adding exchange asset
…structions for enabling logging in CloudHub 2.0 and Runtime Fabric. Include important notes on the use of `INSECURE-LOGGING` to ensure user awareness of potential sensitive information exposure during debugging.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
…w sections on common issues and errors, including deployment problems, registry key conflicts, and broker response behaviors. Provide detailed resolutions and best practices to improve user understanding and troubleshooting efficiency.
… gateway:: component Applies the W-22727519 fix to the versioned 1.0 and 2.0 copies of af-agent-networks.adoc, since the original file was relocated on this branch and would otherwise drop the upstream xref correction.
…twork-2.0-content-ie
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
1 participant
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.
IMPORTANT: for agent network v2 release--GA 6/30
Summary:
Adds new agent-network/2.0/ Antora component with full 2.0 documentation: overview, get-started, create, deploy, publish, troubleshoot, CI/CD, plus full agent-network.yaml and Agent Script references
Splits prior content into a versioned agent-network/1.0/ component and removes the old top-level modules/ROOT/ agent-network pages
Adds new architecture diagrams, IT Investigation Broker example, and updated assets