Update blobstore and communty docs#906
Conversation
|
Warning Review limit reached
More reviews will be available in 52 minutes and 52 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more credits in the billing tab to continue. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (5)
WalkthroughThe pull request updates several BOSH documentation files. 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@content/create-release.md`:
- Around line 690-695: In the warning block titled "Managing split-configuration
between `private.yml` and `final.yml`", fix the subject-verb agreement error in
the sentence beginning with "the value of `/blobstore/<provider>/`". Change
"take precedence over" to "takes precedence over" so that the plural verb agrees
with the singular subject "value". This same grammar fix should also be applied
to the duplicate warning text in `release-blobstore.md` to maintain consistency
across both files.
In `@content/release-blobstore.md`:
- Around line 13-20: The warning block in the release-blobstore.md file contains
a subject-verb agreement error. The phrase "the value of
`/blobstore/<provider>/` in `private.yml` is shallow-merged with, and take
precedence over" uses the plural verb "take" with the singular subject "value".
Change "take" to "takes" to ensure proper grammatical agreement between the
subject and both verbs in the compound predicate.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: 3d72e0cc-17f3-4ca7-af82-b3ab934beae5
📒 Files selected for processing (5)
content/community.mdcontent/create-release.mdcontent/package-vendoring.mdcontent/release-blobstore.mdmkdocs.yml
- Add note to differentiate release- and director blobstore. There's a cross reference from the Director Blobstore docs to the Release Blobstore docs, but not the other way around. - Warn on the potential publishing of blobstore secrets. CLI v2 does not force users to put sensitive blobstore options (e.g. `secret_access_key`) in private.yml. Hence, we should document how CLI v2 actually uses `private.yml` and `final.yml`, and the potential footgun. - Remove incorrect docs on Azure support for Release Blobstore. Although the BOSH Director + BOSH Agent supports Azure blobstore, CLIv2 [doesn't share blobstore support parity](https://github.com/cloudfoundry/bosh-cli/blob/27b76482223696f45c8269d233a3cdd42cdb77a3/releasedir/provider.go#L114-L125 Signed-off-by: Rifa Achrinza <25147899+achrinza@users.noreply.github.com>
- Point roadmap from defunct Pivotal Tracker to GitHub Project - Remove references to no-longer-used `cloudfoundry-incubator` and `bosh-packages` GitHub organisations - Revive with an archive link for now-defunct "Ultimate Guide to BOSH" Signed-off-by: Rifa Achrinza <25147899+achrinza@users.noreply.github.com>
7c42efb to
c28449d
Compare
This PR is two changes, one commit each: