Make pxc-release optional in use-compiled-releases ops file#1299
Open
jochenehret wants to merge 1 commit intodevelopfrom
Open
Make pxc-release optional in use-compiled-releases ops file#1299jochenehret wants to merge 1 commit intodevelopfrom
jochenehret wants to merge 1 commit intodevelopfrom
Conversation
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.
iaftab-alam
approved these changes
Jan 20, 2026
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
2 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?
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. Note that this change requires an enhancement in the runtime-ci "update" tasks: cloudfoundry/runtime-ci#613
What customer problem is being addressed? Use customer persona to define the problem e.g. Alana is unable to...
Alana wants to apply the "use-compiled-releases.yml" ops file in any order with other ops files.
Please provide any contextual information.
#1297 (remove pxc-release in "use-postgres.yml" ops file)
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?
The "pxc-release" is now marked as optional in the use-compiled-releases.yml ops file. This fixes a regression when the use-postgres.yml ops file is applied before use-compiled-releases.yml.
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?
The "cf-deployment" validation passes and the update-pxc Concourse job works.
What is the level of urgency for publishing this change?