SAP-samples / SAP-samples/cf-mta-examples
blue-green strategy does not keep existing service bindings
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 153
- Forks
- 53
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I tried blue-green deployment strategy with
modules:
- name: myName
parameters:
keep-existing:
service-bindings: true
but service bindings were not transferred to the new "-idle" instance of the app.
When I try the same without "blue-green" strategy the existing, manually created service bindings are unbound and rebound as expected.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the blue-green deployment with the shown keep-existing service-bindings configuration, then compare it with the non-blue-green strategy described in the report. Done means manually created service bindings are transferred to the new “-idle” instance; the payload names no source files or tests.
Written by the indexing model from the issue text.
Assessment
- Domain
- cloud, devops
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100