cloudfoundry / cloudfoundry/multiapps-cli-plugin
Inconsistencies in creating an instance from a Service Offering
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 87
- Forks
- 42
- Avg merge
- 17d 21h
- Merged PRs (30d)
- 1
Description
Description
We deployed our Apps to the CF environment which has dependencies in creating an instance of a Service Offering. Now we want to update Plan of an existing service instance by running another cf deploy ... command but we observed some inconsistencies in updating the existing service instance.
In the first place we observed that it tried to update the Plan but provided an empty parameter {} although we pass a parameter. After receiving an error from the Service Broker it retries but this time it passes the correct parameter in the request but with the existing (old) Plan. Due to a parameter validation which we have in our Service Broker the second retry also failed.
Your environment
- MultiApps CF CLI Plugin version - 3.2.2
- which CF vendor is used - SAP
Steps to reproduce
- Deploy an app which has a dependency to a Service.
- Update the Plan of the service in the mtaext yaml file and execute another
cf deploy ...command to update the Plan of the existing Service.
Contributor guide
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 with the service-instance update flow invoked by cf deploy when a dependency's Plan changes in the mtaext YAML file. Reproduce the deployment against a Cloud Foundry environment and inspect the Service Broker requests; done means the update uses the provided parameters and the new Plan consistently without a failing retry using the old Plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100