Generate the enrollment details on launcher startup #2045

cesarfda · 2025-01-14T16:47:47Z

This pull request introduces new functionality for managing enrollment details and updates several mocks in the knapsack package. The key changes include adding methods for setting and getting enrollment details, moving EnrollmentDetails to a new location, and updating the mocks accordingly.

Open Questions:

For autoupdate tests, I changed the tests to use a real osquery binary to validate the GetOsqEnrollDetails. I believe I could achieve similar coverage using Mock.Querier in the tests so we don't make the tests flaky by introducing a dependency.
In autoupdate I chose to get the enrollment details right before the restart. There is also the option of moving that into other steps of the Autoupdater assuming the enrollment details don't change between steps.
Also, with the current setup running before the restart the timeout used for the GetEnrollmentDetails backoff might add additional time to the restart, I set the default to 30 seconds because it was what was used when the code lived in the osquery extension but I could make it shorter so we don't hold the restart for too long.

New Functionality for Enrollment Details:

cmd/launcher/launcher.go: Added logic to retrieve and set runtime enrollment details, including a retry mechanism with backoff for fetching osquery enrollment details.
ee/agent/knapsack/knapsack.go: Introduced SetEnrollmentDetails and GetEnrollmentDetails methods to manage enrollment details.
ee/agent/types/enrollment.go: Moved EnrollmentDetails struct from the service package to the types package, and defined EnrollmentStatus constants.
ee/agent/types/knapsack.go: Updated the Knapsack interface to include methods for managing enrollment details.

Updates to Mocks:

ee/agent/types/mocks/knapsack.go: Added mock implementations for the new GetEnrollmentDetails and SetEnrollmentDetails methods. [1] [2]
ee/agent/types/mocks/flags.go: Removed several unused mock methods related to osquery endpoints.

These changes enhance the functionality and maintainability of the knapsack package by providing a standardized way to handle enrollment details and updating the mocks to reflect the new methods.

Updates to Autoupdate:

New Functionality

Added collectAndSetEnrollmentDetails method to preserve system state during updates
Integrated configurable backoff mechanism for enrollment collection
Enhanced restart process with enrollment data preservation

Code Structure

ee/tuf/autoupdate.go:
- Added enrollment collection before launcher restarts
- Implemented configurable backoff timing
- Enhanced error handling and logging

Test Improvements

ee/tuf/autoupdate_test.go:
- Added real osqueryd binary integration
- Implemented configurable test timeouts
- Enhanced test coverage for enrollment collection
- Added table-driven tests for various scenarios

Configuration Options

Added WithOsquerierBackoff for flexible timing control
Implemented production-ready default values
Added test-specific timing configurations

… and update related methods

…lmentDetails

…rollmentDetails struct to types

…entation

…ith real osquery

…tails

directionless

nice

cmd/launcher/launcher.go

ee/agent/knapsack/knapsack.go

ee/tuf/autoupdate.go

directionless · 2025-01-15T02:39:16Z

ee/tuf/autoupdate.go

@@ -528,6 +541,15 @@ func (ta *TufAutoupdater) checkForUpdate(binariesToCheck []autoupdatableBinary)
 	if updatedVersion, ok := updatesDownloaded[binaryLauncher]; ok {
 		// Only reload if we're not using a localdev path
 		if ta.knapsack.LocalDevelopmentPath() == "" {
+			ctx := context.Background()


I'll defer to becca, but I'm not sure this is the right place

Thinking...we have both LauncherVersion and OsqueryVersion inside the enrollment details, so that's why I'd wanted it updated after autoupdate. If we want to keep it here for that reason, then it probably makes more sense to only update EnrollmentDetails.LauncherVersion and EnrollmentDetails.OsqueryVersion -- we don't need to regenerate the rest of the enrollment details at this time. What do you think?

RebeccaMahany

Nice work! Left a couple comments, will continue to keep an eye on the discussion about where we want to update launcher/osquery version 🙂

cmd/launcher/launcher.go

RebeccaMahany · 2025-01-15T16:56:07Z

cmd/launcher/launcher.go

+			)
+		}
+		return err
+	}, 30*time.Second, 5*time.Second); err != nil {


This can delay launcher startup for up to 30 seconds -- I think we probably don't want to do that. Maybe we should call getEnrollmentDetails in a goroutine so that it doesn't halt startup? (We would probably want to make knapsack.enrollmentDetails nullable -- var enrollmentDetails *types.EnrollmentDetails -- and then have extension.Enroll wait for those details to be available.)

cmd/launcher/launcher.go

ee/agent/types/enrollment.go

ee/agent/knapsack/knapsack.go

ee/tuf/autoupdate.go

RebeccaMahany · 2025-01-15T17:10:39Z

ee/tuf/autoupdate.go

@@ -528,6 +541,15 @@ func (ta *TufAutoupdater) checkForUpdate(binariesToCheck []autoupdatableBinary)
 	if updatedVersion, ok := updatesDownloaded[binaryLauncher]; ok {
 		// Only reload if we're not using a localdev path
 		if ta.knapsack.LocalDevelopmentPath() == "" {
+			ctx := context.Background()


Thinking...we have both LauncherVersion and OsqueryVersion inside the enrollment details, so that's why I'd wanted it updated after autoupdate. If we want to keep it here for that reason, then it probably makes more sense to only update EnrollmentDetails.LauncherVersion and EnrollmentDetails.OsqueryVersion -- we don't need to regenerate the rest of the enrollment details at this time. What do you think?

ee/agent/knapsack/knapsack.go

cesarfda · 2025-01-25T14:12:36Z

I'm starting over to make the changes simpler. I'll also add a requirement of not caching the quick look up part of the call and focus the caching only on the osquery details

cesarfda added 7 commits January 6, 2025 16:46

Refactor enrollment details handling: move EnrollmentDetails to types…

5cb998c

… and update related methods

Update GetEnrollmentDetails to return error and handle it in SetEnrol…

1b258aa

…lmentDetails

Enhance enrollment details retrieval with retry mechanism and move En…

9ac8a8b

…rollmentDetails struct to types

Add SetEnrollmentDetails method to Knapsack interface and mock implem…

ee1a0d8

…entation

Collect and set enrollment details before launcher restart, testing w…

f0a3c8a

…ith real osquery

added edge case coverage and sped up test

25e9a93

Merge remote-tracking branch 'upstream/main' into cesar/enrollment_de…

a9b91ab

…tails

cesarfda linked an issue Jan 14, 2025 that may be closed by this pull request

Include enrollment details in /id response #1986

Open

4 tasks

cesarfda added the features-improvements Features and Improvements label Jan 14, 2025

use context for logging enrollment details update

828f91e

directionless reviewed Jan 15, 2025

View reviewed changes

refactor: extract enrollment details retrieval into a separate function

872e0bf

RebeccaMahany reviewed Jan 15, 2025

View reviewed changes

refactor: enhance enrollment details handling and collection process

c2bb734

directionless reviewed Jan 22, 2025

View reviewed changes

ee/agent/knapsack/knapsack.go Outdated Show resolved Hide resolved

cesarfda added 2 commits January 22, 2025 14:02

refactor: simplify enrollment details update logic and improve logging

2301f53

test: increase timeout for CollectAndSetEnrollmentDetails in tests

4041c4c

cesarfda closed this Jan 25, 2025

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Generate the enrollment details on launcher startup #2045

Generate the enrollment details on launcher startup #2045

cesarfda commented Jan 14, 2025 •

edited

Loading

directionless left a comment

directionless Jan 15, 2025

RebeccaMahany Jan 15, 2025

RebeccaMahany left a comment

RebeccaMahany Jan 15, 2025

RebeccaMahany Jan 15, 2025

cesarfda commented Jan 25, 2025

Generate the enrollment details on launcher startup #2045

Generate the enrollment details on launcher startup #2045

Conversation

cesarfda commented Jan 14, 2025 • edited Loading

Open Questions:

New Functionality for Enrollment Details:

Updates to Mocks:

Updates to Autoupdate:

New Functionality

Code Structure

Test Improvements

Configuration Options

directionless left a comment

Choose a reason for hiding this comment

directionless Jan 15, 2025

Choose a reason for hiding this comment

RebeccaMahany Jan 15, 2025

Choose a reason for hiding this comment

RebeccaMahany left a comment

Choose a reason for hiding this comment

RebeccaMahany Jan 15, 2025

Choose a reason for hiding this comment

RebeccaMahany Jan 15, 2025

Choose a reason for hiding this comment

cesarfda commented Jan 25, 2025

cesarfda commented Jan 14, 2025 •

edited

Loading