cloudfoundry / cloudfoundry/stratos
cf push: Support disconnected environments
Open
Nobody has claimed this yet.
feature-request
- Dominant language
- TypeScript
- Stars
- 267
- Forks
- 137
- Avg merge
- 5h 14m
- Merged PRs (30d)
- 77
Description
- prebuild target
- runs current prebuild-ui
- should also fetch backend deps
- this process is dependent on the stack
- could prebuild for linux and make them available publicly
- could provider docker environment to build
- etc
- disable features given disconnected state
- app deployment types like github, gitlab, etc
- would we need to do something for our custom build back?
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 the existing prebuild-ui target and the cf push deployment paths mentioned in the issue. Trace how backend dependencies and app deployment types such as GitHub and GitLab are handled in disconnected environments, including custom buildpacks. Done should include a defined approach for dependency availability and behavior for unsupported disconnected features.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- build-system, cloud, devops
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100