Fleet version: Observed in Fleet's dogfood environment (commit c6859c6)
💥 Actual behavior
After adding a configuration profile with "Label A" (name) added as a custom target, I changed the label's name to "Label B"
When viewing the profile on the Controls > OS settings > Custom settings page, the profile still shows "Label A"
🕯️ More info (optional)
The GET /configuration_profiles API endpoint also returns the old label name: "Label A"
So, we think this needs a backend fix.
Fleet version: Observed in Fleet's dogfood environment (commit
c6859c6)💥 Actual behavior
After adding a configuration profile with "Label A" (name) added as a custom target, I changed the label's name to "Label B"
When viewing the profile on the Controls > OS settings > Custom settings page, the profile still shows "Label A"
🕯️ More info (optional)
The
GET /configuration_profilesAPI endpoint also returns the old label name: "Label A"So, we think this needs a backend fix.