cloudfoundry / cloudfoundry/cloud_controller_ng
Add a test to CATs to cover service binding parameters not being passed in
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 207
- Forks
- 373
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 56
Description
Context
Last week (March 24th) a PR was introduced to fix an issue where service binding parameters were not passed in on the apply manifest stage, this would mean that customers who pass in required parameters in as binding params would experience a break. We were asked by folks on the platform team to add a CATs test to cover this case.
Ask
Open a PR to CATs with a new test which makes sure that binding parameters are passed in on the apply manifest step (add the params to an app manifest, and validate they propagate to the broker on cf push)
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 by locating the CATs test suite and existing service-binding or apply-manifest cases. Add a scenario with binding parameters in an app manifest, then run the relevant CATs test to verify that the parameters reach the broker during cf push.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100