cloudfoundry / cloudfoundry/docs-cf-admin
Update BOSH deployment manifest instructions for adding an isolation segment for cf-deployment
Nobody has claimed this yet.
- Dominant language
- HTML
- Stars
- 18
- Forks
- 112
- PR merge metrics
- No merged PRs in 30d
Description
As noted in the CFF Slack workspace at https://cloudfoundry.slack.com/archives/C02FL4A2K/p1528132160000151 (#general, 2018-06-04), the example of the manifest changes at https://docs.cloudfoundry.org/adminguide/isolation-segments.html#bosh-segments is out of date now that the cf-deployment has replaced the previous manifest-generation system. Something like https://github.com/cloudfoundry/cf-deployment/blob/683f5044781f600104f6cc9e5a4e13d200d35c77/operations/test/add-persistent-isolation-segment-diego-cell.yml#L50-L51 is more relevant.
I'm happy to work with the Docs team to update these instructions, but I don't have time right now to PR a change in myself.
Also /cc @heyjcollins @dsabeti
Contributor guide
No contributing guide indexed for this repository
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 with the BOSH isolation-segments instructions at docs.cloudfoundry.org/adminguide/isolation-segments.html#bosh-segments and compare the example with the linked cf-deployment operations file, especially lines 50-51. Done means the documentation shows current cf-deployment manifest instructions for adding an isolation segment.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- html, yaml
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 52/100