consider transport modes for transport flow decisions #516
Conversation
This file contains 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
morri-son
approved these changes
Sep 22, 2023
There was a problem hiding this comment.
@mandelsoft, approved. Please check if the next integration test runs successfully through
robertwol
pushed a commit
that referenced
this pull request
Sep 25, 2023
* consider transport modes for transport flow decisions * follow references even for skipped local transport * fix overwrite mode keeping local access if required --------- Co-authored-by: Gerald Morrison <67469729+morri-son@users.noreply.github.com>
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.
What this PR does / why we need it:
To decide, which resources have to be transported the digest is not sufficient to handle re-transports
of exactly the same content with different transport modes (value vs reference).
This Pr checks, whether access methods would have to be changed according to the
the actual state in the target repository and the chosen transport mode. This then
controls the transport flow of a dedicated component version.
Additionally it should also handle the preserving of existing artifacts for overwrite transports.
There are several new tests now for those scenarios.
Which issue(s) this PR fixes:
Fixes #513
Special notes for your reviewer:
Release Notes: