cloudfoundry / cloudfoundry/cloud_controller_ng
App ports support within the manifest
Nobody has claimed this yet.
- Dominant language
- Ruby
- Stars
- 207
- Forks
- 373
- Avg merge
- 2d 12h
- Merged PRs (30d)
- 56
Description
Hi CAPI people,
I would like to create an app with multiple app ports and attached routes. I don't wont to go the extra mile by calling several additional CLI commands but instead have the support directly within the manifest itself.
Calling multiple CLI commands is cumbersome and error-prone and using a single manifest is much more user-friendly.
If you need more context: There was already a discussion on the whole app ports and routes situation at https://github.com/cloudfoundry/routing-release/issues/152 and it was mentioned that the CAPI team is responsible for the development of the manifest.
In case there are work packages that can be done by an "outsider" like me, feel free to contact me and I would be glad to help. ☺️
Thanks in advance for any help that pushes this topic further.
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 reviewing this issue and the linked routing-release discussion at routing-release/issues/152 to understand the existing app-port and route requirements. The issue does not name implementation files, tests, or a defined manifest schema; completion would require agreeing on the manifest support and its expected behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ruby
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100