Add GitOps name_template under controls#48892
Conversation
Codecov Report❌ Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## 38806-macos-iosipados-rename-hosts #48892 +/- ##
=====================================================================
Coverage ? 68.04%
=====================================================================
Files ? 3683
Lines ? 234297
Branches ? 12419
=====================================================================
Hits ? 159422
Misses ? 60529
Partials ? 14346
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
8ca08a1 to
a982acb
Compare
|
@coderabbitai full review |
✅ Action performedFull review finished. |
Relates to #48625 Lets GitOps own the host name template via controls.name_template in team YAML. Parsed into GitOpsControls (with type validation and Set() presence check), applied declaratively through the same team-spec path as the endpoint (absent key clears the template), and rejected for org-level and no-team controls. generate-gitops emits name_template for real fleets (fleets-only: omitted for org and No team) so a generate -> apply round-trip preserves a set template rather than silently clearing it — same declarative contract as enable_disk_encryption.
a982acb to
ef83dc9
Compare
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (7)
WalkthroughThis PR adds support for a new Possibly related issues
Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches📝 Generate docstrings
🧪 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 |
adb1cc7
into
38806-macos-iosipados-rename-hosts
Relates to #48625
Lets GitOps own the host name template via controls.name_template in team YAML. Parsed into GitOpsControls (with type validation and Set() presence check), applied declaratively through the same team-spec path as the endpoint (absent key clears the template), and rejected for org-level and no-team controls. generate-gitops emits controls field-by-field and does not include name_template, so it does not round-trip (matches the story's 'No changes' for generation).
Related issue: Resolves #
Checklist for submitter
If some of the following don't apply, delete the relevant line.
Testing
Summary by CodeRabbit
New Features
Bug Fixes