Make okta and jamf properties snake_case#324
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (31)
WalkthroughJamf and Okta documentation now uses snake_case property names in node tables and sample YAML, and the Jamf/Okta queries now reference the renamed properties. ChangesJamf and Okta snake_case doc sync
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~25 minutes Poem
🚥 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 |
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
jeff-matthews
left a comment
There was a problem hiding this comment.
Looks good @JonasBK! Thanks for the PR. Is it ok to merge and publish right away?
|
@jeff-matthews, yup! Thanks! |
The first iteration of the OG collectors for Okta and Jamf created properties in camelCase. OpenHound use snake_case. This PR will align with OpenHound.
Summary by CodeRabbit
snake_caseproperty names across node tables and sample values.tier,site_id,okta_domain, and other renamed fields.