cloudfoundry / cloudfoundry/stratos
Deploy application: Handle apps where the manifest lives outside of repo
Open
Nobody has claimed this yet.
feature-request
- Dominant language
- TypeScript
- Stars
- 267
- Forks
- 137
- Avg merge
- 5h 14m
- Merged PRs (30d)
- 77
Description
As a follow on from https://github.com/cloudfoundry-incubator/stratos/issues/1442 we should also look at catering for apps where the manifest is not in the repo. Usually this is handled by cf push -f .
Suggestion..
- Provide a way for the user to specify a manifest within the deploy process
- save manifest where we fetch the repo
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 the deploy process where the repository is fetched and compare it with the cf push -f workflow described in the issue. Define how a user specifies a manifest outside the repository and verify that the manifest is saved alongside the fetched repository and used during deployment.
Written by the indexing model from the issue text.
Assessment
- Domain
- cloud
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100