-
Notifications
You must be signed in to change notification settings - Fork 905
VPP Token Assignment and GitOps Issue #32432
Copy link
Copy link
Closed
Labels
#g-mdmMDM product groupMDM product group:releaseReady to write code. Scheduled in a release. See "Making changes" in handbook.Ready to write code. Scheduled in a release. See "Making changes" in handbook.bugSomething isn't working as documentedSomething isn't working as documentedcustomer-eponymcustomer-kokkola
Milestone
Metadata
Metadata
Assignees
Labels
#g-mdmMDM product groupMDM product group:releaseReady to write code. Scheduled in a release. See "Making changes" in handbook.Ready to write code. Scheduled in a release. See "Making changes" in handbook.bugSomething isn't working as documentedSomething isn't working as documentedcustomer-eponymcustomer-kokkola
Type
Fields
Give feedbackNo fields configured for issues without a type.
Projects
StatusShow more project fields
Done
Fleet version: 4.72.0
💥 Actual behavior
customer-kokkolastated that when attempting to configure VPP assignment via gitops they receive an error for an existing team, there is however no error when performing a dry-run of the same gitops update.Error Message
🛠️ To fix
Product designer: @marko-lisica
If running the command without the dry-run flag throws an error, the same error should occur when running with the dry-run flag.
When a team doesn't have a VPP token assigned, we see the expected error in GitOps when adding
app_store_appsto a team YAML file. We should see the same error when running command with--dry-runflag.🧑💻 Steps to reproduce
🕯️ More info (optional)
Slack Threads
https://fleetdm.slack.com/archives/C08HNQD4XP1/p1756381134939989
https://fleetdm.slack.com/archives/C019WG4GH0A/p1756313045609699