This repository has been archived by the owner on Jul 18, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* add README * add a client API to fetch server components * add inventory api placeholder functions Add in API endpoints and the beginning of handler functions for converting incoming common.Device objects into FleetDB server records. * Initialize the client library (#6) * initialize the client library * refactor minor * internal fleetdb outline (#9) * Move types ownership to alloy (#11) * fix panic when there's no response (#12) * Convert Alloy Data to Rivets.Server (#16) * type converter * typo * Forward Inventory to FleetDB (#19) * forward inventory to fleetdb * cleanup code * rebase (#20) * use bmc-toolbox component types (#21) * update dependencies --------- Co-authored-by: Alva Zhang <140438385+Alva8756@users.noreply.github.com>
- Loading branch information
Showing
18 changed files
with
2,859 additions
and
165 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,7 @@ | ||
### Component Inventory Service | ||
This is the code for the service sitting between Alloy and other consumers of | ||
component data. It exists to synthesize a common union of facts discovered | ||
by each of Alloys operating modes (`in-band` and `out-of-band`). These modes | ||
refer to whether component data collection was performed in the host by an | ||
application or if the survey was completed via the BMC of the server. | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.