Remove "pxc" release if Postgres is used#1297
Merged
jochenehret merged 1 commit intodevelopfrom Dec 30, 2025
Merged
Conversation
iaftab-alam
approved these changes
Dec 30, 2025
jochenehret
added a commit
to cloudfoundry/cf-performance-tests-pipeline
that referenced
this pull request
Jan 14, 2026
* PR cloudfoundry/cf-deployment#1297 removes pxc-release if Postgres is used, but has unfortunately the side-effect that "use-compiled-releases.yml" has to be applied before "use-postgres.yml" * change order as a workaround
jochenehret
added a commit
that referenced
this pull request
Jan 15, 2026
In the "use-postgres.yml" ops file, we've removed the pxc-release: #1297. This has however the side-effect that "use-compiled-releases.yml" has to be applied *before* "use-postgres.yml". Otherwise, bosh-interpolate will fail. This commit makes the pxc-release optional.
10 tasks
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
3 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.
WHAT is this change about?
Remove "pxc-release" when "use-postgres.yml" ops file is used.
What customer problem is being addressed? Use customer persona to define the problem e.g. Alana is unable to...
Alana does not want to create all the packages of the pxc-release when using Postgres.
Please provide any contextual information.
Has a cf-deployment including this change passed cf-acceptance-tests?
Does this PR introduce a breaking change? Please take a moment to read through the examples before answering the question.
How should this change be described in cf-deployment release notes?
Remove "pxc-release" in "use-postgres.yml" ops file. This saves compilation time.
Does this PR introduce a new BOSH release into the base cf-deployment.yml manifest or any ops-files?
Does this PR make a change to an experimental or GA'd feature/component?
Please provide Acceptance Criteria for this change?
"cf-deployment" validation pipeline must be green.
What is the level of urgency for publishing this change?