feat: initial job property validation docs#915
Conversation
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
WalkthroughUpdates job specification documentation with a YAML example title and a property validation section covering BOSH version requirements, Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ 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/jobs.md`:
- Around line 111-112: Insert a blank line between the `---` separator and the
`## Property validation` heading in the property-validation section, preserving
the heading and separator unchanged.
- Around line 132-139: Update the trusted_certificate property in
properties-schema.json to use the valid JSON Schema type "string" instead of
"certificate"; preserve any certificate-specific requirements through separate
validation or description metadata.
🪄 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: 4fbd9741-2a4a-4ea1-b892-432454065c91
📒 Files selected for processing (1)
content/jobs.md
afcdff8 to
cc69f46
Compare
|
@coderabbitai review |
✅ Action performedReview finished.
|
There was a problem hiding this comment.
Pull request overview
Documents BOSH release job property validation by introducing a new “Property validation” section in the release jobs documentation, including version requirements and example JSON Schemas.
Changes:
- Adds a dedicated “Property validation” section describing how job properties can be validated via JSON Schema.
- Includes example schema files and a BOSH-specific JSON Schema
certificatetype extension. - Improves/clarifies existing wording around job spec property keys and validation.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
57ca4c9
|
@achrinza - could you rebase this, there appear to be conflicts. Thanks! |
Document BOSH release job property validation see: cloudfoundry/community#1049 see: cloudfoundry/bosh-cli#681 see: cloudfoundry/bosh#2602 Signed-off-by: Rifa Achrinza <25147899+achrinza@users.noreply.github.com>
Signed-off-by: Rifa Achrinza <25147899+achrinza@users.noreply.github.com>
57ca4c9 to
c1e9d04
Compare
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 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/jobs.md`:
- Around line 148-149: Update the BOSH custom certificate type description to
state that validation accepts values parseable by
OpenSSL::X509::Certificate.load, including PEM or DER encodings, rather than
requiring PEM-encoded X.509 v3 certificates. Explicitly document that an empty
string is accepted if this behavior is intentional.
🪄 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: 10940be6-3ada-401e-be03-26a33bd7e8f0
📒 Files selected for processing (1)
content/jobs.md
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 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/jobs.md`:
- Around line 127-128: Update the wording in the deployment validation
description to refer to a “JSON Schema” rather than a “JSON Schema instance,”
while preserving the existing explanation of Director-enforced validation during
BOSH deployments.
🪄 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: cbd74844-55af-4ab7-a9eb-fd3086c7d1b5
📒 Files selected for processing (1)
content/jobs.md
- Document restriction to Draft 2020-12 - Explain zero-string validity for `type: "certificate"` - Fix incorrect `JSON Schema instance` to `JSON Schema document` Signed-off-by: Rifa Achrinza <25147899+achrinza@users.noreply.github.com>
3217984 to
4c4455f
Compare
Document BOSH release job property validation
see: cloudfoundry/community#1049
see: cloudfoundry/bosh-cli#681
see: cloudfoundry/bosh#2602