Repository navigation
Conversation
Replace the inbound/outbound data flow examples, which no longer exist, with blueprint flow source/destination, and drop "or service" since services are components in 2.0. Fixes CycloneDX#1204 Fixes CycloneDX#1083 Signed-off-by: Srinivas Chippagiri <cvas22@gmail.com>
jkowalleck
marked this pull request as draft
November 12, 2026 11:09
Member
|
put on draft; the proposed solution in #1204 needs to be discussed first. |
Member
cvas22
marked this pull request as ready for review
November 13, 2026 09:20
This branch has not been deployed
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
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.
I went with the wording you suggested in #1204, so input
sourceand outputtargetnow point at a blueprint flow'ssource/destinationinstead of the old inbound/outbound values. While there I dropped "or service" from the rest of the formulation descriptions since services are components in 2.0, which covers the formulation part of #1115 too. Descriptions only, no schema changes.