Repository navigation
Conversation
Adds the DryRunResult schema and wires dryRunResult/outputs onto the Operation model and mtarest.yaml, consumed by the dry-run deploy flow.
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.
Description:
Adds dry-run support to the deploy workflow. When
--dry-runis passed, thedeployment runs through the full planning phase but all CF Cloud Controller
write calls are intercepted by
DryRunCloudControllerClient, which recordsintended changes without applying them.
What changes:
DryRunCloudControllerClientwraps the real client and capturesapps/services/routes that would be created, updated, or deleted.
DryRunChangeSetcollects those records and is stored as a process variable.DryRunResultmodel added to the API;OperationgainsdryRunResultandoutputsfields so callers can read the predicted changeset after theoperation completes.
--dry-runparameter wired intoDeployMetadataand the BPMN deploy flows(
deploy-app.bpmn,xs2-deploy.bpmn,process-batches-sequentially.bpmn).Design choices:
records every write call, so the planning steps run unmodified.
operation response at the end, keeping it out of the hot path.
Issue:
LMCROSSITXSADEPLOY-3716