document (or improve docs) for complex MDM flows

[roperzh]

Goal

User story
As a fleet contributor,
I want to understand how fleet works
so that I can contribute efficiently, even if the person that implemented the complex feature is not around.

Context

• Requestor(s): @roperzh
• Product designer: @georgekarrv

Changes

Engineering

The following flows are hard to understand and not documented or poorly documented:

• [ ] ADE with SSO + user configuration
• [ ] Profile/declaration reconciliation and cron
• [ ] JSON profile assignment

ℹ️  Please read this issue carefully and understand it. Pay special attention to UI wireframes, especially "dev notes".

QA

Risk assessment

• Requires load testing: no
• Risk level: Low , zero

Confirmation

1. [ ] Engineer (@____): Added comment to user story confirming successful completion of QA.
2. [ ] QA (@____): Added comment to user story confirming successful completion of QA.

[lukeheath]

@roperzh Thanks for the great engineering-initiated stories! I'll make sure to review these on my next pass.

[lukeheath]

As we grow our team and MDM efforts, this is an important investment to make sure Roberto's insights are properly documented and shared with other contributors.

I'm prioritizing to the drafting board for estimation. I'm also assigning @georgekarrv as product designer to work with Roberto to determine how the docs should like and where they'll live. I imagine in the contributor docs.

[georgekarrv]

Missed this today in est since I filter on #g-mdm. added and will just ask the team to est tomorrow.

[georgekarrv]

Hey team! Please add your planning poker estimate with Zenhub @dantecatalfamo @ghernandez345 @gillespi314 @jahzielv @roperzh