Skip to content

Add identity-aware-routing to experimental pipeline - #1375

Open
dtasSap wants to merge 4 commits into
cloudfoundry:developfrom
sap-contributions:identitiy-aware-routing-experimental
Open

dtasSap wants to merge 4 commits into
cloudfoundry:developfrom
sap-contributions:identitiy-aware-routing-experimental

Conversation

@dtasSap

@dtasSap dtasSap commented Sep 23, 2026 •

Copy link
Copy Markdown

Please take a moment to review the questions before submitting the PR

🚫 We only accept PRs to develop branch. If this is an exception, please specify why 🚫

WHAT is this change about?

This PR will add the feature identity-aware-routing test to the experimental hermione pipeline

What customer problem is being addressed? Use customer persona to define the problem e.g. Alana is unable to...

RFC

Please provide any contextual information.

This feature was introduced in this PR.
Acceptance tests were added in this PR.

Has a cf-deployment including this change passed cf-acceptance-tests?

  • YES
  • NO

Does this PR introduce a breaking change? Please take a moment to read through the examples before answering the question.

  • YES - please choose the category from below. Feel free to provide additional details.
  • NO

Types of breaking changes:

  1. causes app or operator downtime
  2. increases VM footprint of cf-deployment - e.g. new jobs, new add ons, increases # of instances etc.
  3. modifies, deletes or moves the name of a job or instance group in the main manifest
  4. modifies the name or deletes a property of a job or instance group in the main manifest
  5. changes the name of credentials in the main manifest
  6. requires out-of-band manual intervention on the part of the operator
  7. modifies the ops-file path, changes the type, changes the values or removes ops-files from the following folders
    • ./operations/ or ./operations/experimental
    • ./addons
    • ./backup-and-restore/

If you're promoting an experimental Ops-file (or removing one), Please follow the Ops-file workflows.

Ops files changes in the following folders are considered as NON BREAKING CHANGES
./community, ./example-vars-files, ./test

How should this change be described in cf-deployment release notes?

Something brief that conveys the change and is written with the persona (Alana, Cody...) in mind. See previous release notes for examples.

Does this PR introduce a new BOSH release into the base cf-deployment.yml manifest or any ops-files?

  • YES - please specify
  • NO

Does this PR make a change to an experimental or GA'd feature/component?

  • experimental feature/component
  • GA'd feature/component

Please provide Acceptance Criteria for this change?

The experimental-cats test job in the hermione pipeline should run through without any errors.

What is the level of urgency for publishing this change?

  • Urgent - unblocks current or future work
  • Slightly Less than Urgent

Tag your pair, your PM, and/or team!

It's helpful to tag a few other folks on your team or your team alias in case we need to follow up later.

@dtasSap
dtasSap marked this pull request as ready for review September 23, 2026 11:59
@iaftab-alam
iaftab-alam requested a review from a team September 23, 2026 12:09
Comment thread ci/pipelines/cf-deployment.yml Outdated
@dtasSap
dtasSap requested a review from jochenehret September 23, 2026 13:03
jochenehret
jochenehret previously approved these changes Sep 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants