Skip to content
This repository has been archived by the owner on Jul 18, 2024. It is now read-only.

Outline of the internal fleetdb interaction #9

Merged
merged 1 commit into from
Mar 18, 2024
Merged

Conversation

Alva8756
Copy link
Contributor

What does this PR do

  • Export type ComponentInventoryDevice for Alloy to send request on wire.
  • Add an internal FleetDB client interface for interacting with FleetDB
    • Draft the UpdateAttributes()

@Alva8756 Alva8756 force-pushed the type branch 3 times, most recently from e898ac0 to 320d6aa Compare March 18, 2024 00:55
if err := fn(
getFleetDBClient(theApp.Cfg),
serverID,
ctx,
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TIL that a *gin.Context fills context.Context

@Alva8756 Alva8756 merged commit 8b5d2ef into vc/query-api Mar 18, 2024
4 checks passed
@Alva8756 Alva8756 deleted the type branch March 18, 2024 16:35
DoctorVin added a commit that referenced this pull request May 1, 2024
* 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>
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants