-
Notifications
You must be signed in to change notification settings - Fork 468
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add multiple Apple Business Manager and Volume Purchasing Program connections #9956
Comments
@zayhanlon @zwass We didn't get to this one in the current design sprint. Adding it to feature fest. |
Hey @dherder, heads up, we didn't have room to take this one in the current design sprint (4.48). |
We now also have a European MSP (confidential) that requires same set of features and willing to work with us on developing and bringing to market |
> Related issue: #9956 # Checklist for submitter If some of the following don't apply, delete the relevant line. <!-- Note that API documentation changes are now addressed by the product design team. --> - [x] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. See [Changes files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/Committing-Changes.md#changes-files) for more information. - [x] Input data is properly validated, `SELECT *` is avoided, SQL injection is prevented (using placeholders for values in statements) - [x] Added/updated tests - [x] If paths of existing endpoints are modified without backwards compatibility, checked the frontend/CLI for any necessary changes - [x] If database migrations are included, checked table schema to confirm autoupdate - For database migrations: - [x] Checked schema for all modified table for columns that will auto-update timestamps during migration. - [x] Confirmed that updating the timestamps is acceptable, and will not cause unwanted side effects. - [x] Ensured the correct collation is explicitly set for character columns (`COLLATE utf8mb4_unicode_ci`). - [x] Manual QA for all new/changed functionality --------- # Checklist for submitter If some of the following don't apply, delete the relevant line. <!-- Note that API documentation changes are now addressed by the product design team. --> - [ ] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. See [Changes files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/Committing-Changes.md#changes-files) for more information. - [ ] Input data is properly validated, `SELECT *` is avoided, SQL injection is prevented (using placeholders for values in statements) - [ ] Added support on fleet's osquery simulator `cmd/osquery-perf` for new osquery data ingestion features. - [ ] Added/updated tests - [ ] If paths of existing endpoints are modified without backwards compatibility, checked the frontend/CLI for any necessary changes - [ ] If database migrations are included, checked table schema to confirm autoupdate - For database migrations: - [ ] Checked schema for all modified table for columns that will auto-update timestamps during migration. - [ ] Confirmed that updating the timestamps is acceptable, and will not cause unwanted side effects. - [ ] Ensured the correct collation is explicitly set for character columns (`COLLATE utf8mb4_unicode_ci`). - [ ] Manual QA for all new/changed functionality - For Orbit and Fleet Desktop changes: - [ ] Orbit runs on macOS, Linux and Windows. Check if the orbit feature/bugfix should only apply to one platform (`runtime.GOOS`). - [ ] Manual QA must be performed in the three main OSs, macOS, Windows and Linux. - [ ] Auto-update manual QA, from released version of component to new version (see [tools/tuf/test](../tools/tuf/test/README.md)). Co-authored-by: Jahziel Villasana-Espinoza <[email protected]> Co-authored-by: Martin Angers <[email protected]> Co-authored-by: Gabriel Hernandez <[email protected]> Co-authored-by: Sarah Gillespie <[email protected]> Co-authored-by: Dante Catalfamo <[email protected]>
> Related issue: #9956 # Checklist for submitter If some of the following don't apply, delete the relevant line. <!-- Note that API documentation changes are now addressed by the product design team. --> - [x] Changes file added for user-visible changes in `changes/`, `orbit/changes/` or `ee/fleetd-chrome/changes`. See [Changes files](https://github.com/fleetdm/fleet/blob/main/docs/Contributing/Committing-Changes.md#changes-files) for more information. - [x] Input data is properly validated, `SELECT *` is avoided, SQL injection is prevented (using placeholders for values in statements) - [x] Added/updated tests - [x] If paths of existing endpoints are modified without backwards compatibility, checked the frontend/CLI for any necessary changes - [x] If database migrations are included, checked table schema to confirm autoupdate - For database migrations: - [x] Checked schema for all modified table for columns that will auto-update timestamps during migration. - [x] Confirmed that updating the timestamps is acceptable, and will not cause unwanted side effects. - [x] Ensured the correct collation is explicitly set for character columns (`COLLATE utf8mb4_unicode_ci`). - [x] Manual QA for all new/changed functionality --------- Co-authored-by: Martin Angers <[email protected]> Co-authored-by: Gabriel Hernandez <[email protected]> Co-authored-by: Roberto Dip <[email protected]> Co-authored-by: Sarah Gillespie <[email protected]> Co-authored-by: Dante Catalfamo <[email protected]> Co-authored-by: Roberto Dip <[email protected]>
@rachaelshaw I passed this one to you during confirm and celebrate. Can you please own closing the remaining checkboxes? Thanks :) |
Hey @rachaelshaw, I just noticed that the reference docs PR has conflicts. Please let me know how/if I can help resolve those. Happy to help! Getting reference docs merged is last item before we can call this story done. |
Hey @rachaelshaw, I resolved the conflicts for the reference doc PR. I left a question for Dante here but I think we can go ahead and merge if everything looks good. Then address any fixes to the redirect a follow up PR. |
Hey @rachaelshaw, just following up w/ another ping! Please let me know if/how I can help get the reference doc PR across the finish line so we can call this story shipped. |
…urchasing Program connections (#21043) GitOps and API changes for the following story: - #9956 DONE: - ~~Contributor API endpoints to support best practice GitOps (`fleetctl gitops`) and backwards compatibility GitOps (`fleetctl apply`)~~ - #21043 (comment) --------- Co-authored-by: Martin Angers <[email protected]> Co-authored-by: Dante Catalfamo <[email protected]> Co-authored-by: Marko Lisica <[email protected]> Co-authored-by: George Karr <[email protected]> Co-authored-by: Gabriel Hernandez <[email protected]> Co-authored-by: Rachael Shaw <[email protected]>
Updates to the permissions guide are in a PR here: Permissions PR is here: #22336 Waiting to closet this story until that is merged. |
Hey @zayhanlon and @dherder heads up that this story w/ customer/prospect labels attached was shipped in 4.56 🚀 We're missing the guide. I filed a bug for this here: #22339 I think let's leave this story open until we ship the guide. |
hey @noahtalerman the guide was already updated here #21627 |
Followed up here: #22339 (comment) |
PR to the guides is up here: #22458 |
Closing this story now that we shipped the best practice in a guide here: https://fleetdm.com/guides/macos-mdm-setup#best-practice |
Apple workflows bloom, |
@noahtalerman Where is the UI for this? I just tried to demo it to a partner and failed to do it, because I couldn't find the option in the UI. I later found it here: How can we make it more visible? |
@mikermcneil maybe we add more "Apple Business Manager" language here in Settings > Integrations > MDM? Clicking the pencil icon is how you get to the ABM page: |
Goal
Context
Changes
Product
fleetctl get apple-bm
if there's one ABM token. Wireframes are in Figma here.Engineering
QA
@noahtalerman:
added by @mna:
added by @PezHub:
Confirm all copy -
End User Authentication -
ABM -
VPP -
Banners VPP & ABM -
GitOps
Miscellaneous -
End-to-end Tests -
The text was updated successfully, but these errors were encountered: