cloudfoundry / cloudfoundry/cloud_controller_ng
V2 to V3 migration: Application custom startup command
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 207
- Forks
- 373
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 56
Description
Issue
V2 to V3 migration: Application custom startup command
Context
In our client application we need to know whether cf application has been started with custom command or not. V2 API provided this information through different ways. One of them is curl -ik "https://[api.url]/v2/apps/[guid]" -X GET -H "Authorization: ..". Application Entity command field contains either custom command or null. This field does not exist in V3 and there is no other way to get this information.
Steps to Reproduce
cf push any-app -c "./custom-start.sh" -f manifest.yml
curl -ik "https://[api.url]/v2/apps/[guid]" -X GET -H "Authorization: .."
curl -ik "https://[api.url]/v3/apps/[guid]" -X GET -H "Authorization: .."
Expected result
Way to get custom command using purely V3 API.
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
Compare the V2 and V3 application endpoints shown in the issue, starting with the application command field and the V3 response shape. Determine where a purely V3 representation could be exposed and define completion as a documented, retrievable way to distinguish custom startup commands from applications without one.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100