cloudfoundry / cloudfoundry/stratos
V3 API: Update app state creation to support new app processes
Open
Nobody has claimed this yet.
v3 api
- Dominant language
- TypeScript
- Stars
- 267
- Forks
- 137
- Avg merge
- 5h 14m
- Merged PRs (30d)
- 77
Description
- Summary state is a combination of
- App
state - App
package_state - App
package_updated_at - App
instances - App Stats instances collection
- App
Now we have to take into account app 1:M processes, processes 1:1 stats. There's also current_droplet state, package state, etc
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 tracing V3 API app state creation and reviewing how the current summary combines app state, package state, package_updated_at, instances, and App Stats instances. Define how app-to-process and process-to-stats relationships, current_droplet state, and package state should be represented; done means the summary accounts for the new app processes consistently.
Written by the indexing model from the issue text.
Assessment
- Domain
- api, backend-api-design
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100