Describe the feature
The coresmd plugin currently implements its own SMD client and define its own models in smdclient package. Ideally, the API for interacting with these models would be provided by the new fabrica-generated client library, but is not currently ready to be used. When the client library is ready, we should replace the current implementation of the smdclient client with the fabrica-generated one.
SMD client: https://github.com/OpenCHAMI/coresmd/blob/main/internal/smdclient/smdclient.go
Why do you want this feature?
This removes the need to maintain multiple separate implementations of the SMD client and make consistent across all of our different services and tools.
Alternatives you've considered
We can keep the current implementations, but that would require more maintenance later.
Additional context
This requires the fabrica-generated "SMD 2" to provide the client library first.
Code of Conduct
Describe the feature
The
coresmdplugin currently implements its own SMD client and define its own models insmdclientpackage. Ideally, the API for interacting with these models would be provided by the newfabrica-generated client library, but is not currently ready to be used. When the client library is ready, we should replace the current implementation of thesmdclientclient with thefabrica-generated one.SMD client: https://github.com/OpenCHAMI/coresmd/blob/main/internal/smdclient/smdclient.go
Why do you want this feature?
This removes the need to maintain multiple separate implementations of the SMD client and make consistent across all of our different services and tools.
Alternatives you've considered
We can keep the current implementations, but that would require more maintenance later.
Additional context
This requires the
fabrica-generated "SMD 2" to provide the client library first.Code of Conduct