Closed noahtalerman closed 1 year ago
Hey team! Please add your planning poker estimate with Zenhub @ghernandez345 @gillespi314 @roperzh
@gillespi314 I thought this morning that I had a better handle on how to test this, but after a couple of discussions I realize I do not. Any chance we can get a call together tomorrow to run through it?
Validated able to successfully start Fleet and enroll a Windows host into MDM with the BYTES
env variables.
Additional testing notes: Tested with incorrect env var formatting and received expected error. Tested with incorrect values set & received expected error. Tested starting with the cert variable set & key flag, received an error. Tested with key variable set & cert flag, was able to run Fleet successfully.
C&C Hey @gillespi314 would you document these changes? cc @noahtalerman
UPDATE: Hey @gillespi314, @ireedy is writing the docs for these changes.
Confirm and celebrate: @ireedy just checking in, how are docs going?
@noahtalerman PR submitted for your review!
C&C: can close!
Config bytes now set, Unblocks Windows MDM test, Progress without fret.
Goal
Changes
FLEET_MDM_WINDOWS_WSTEP_IDENTITY_CERT_BYTES
andFLEET_MDM_WINDOWS_WSTEP_IDENTITY_KEY_BYTES
configuration options. These are the bytes equivalent of the existingFLEET_MDM_WINDOWS_WSTEP_IDENTITY_CERT
andFLEET_MDM_WINDOWS_WSTEP_IDENTITY_KEY
file path options.Context
While the file path options work great during development, it's difficult to have the dogfood environment accept the file path options.
This is just a fix for dogfooding Windows MDM. The plan for launch is to auto magically generate and apply these certs for the user. This will take significant effort and we want to unblock dogfooding sooner.
Engineering
Product quality
Context
QA
Risk assessment
Manual testing steps
Testing notes
Confirmation