mirror of
https://github.com/edgelesssys/constellation.git
synced 2025-07-29 01:58:34 -04:00
versions: consolidate various types of Components
There used to be three definitions of a Component type, and conversion routines between the three. Since the use case is always the same, and the Component semantics are defined by versions.go and the installer, it seems appropriate to define the Component type there and import it in the necessary places.
This commit is contained in:
parent
a8fb6c5af0
commit
a1dbd13f95
25 changed files with 454 additions and 379 deletions
|
@ -2,6 +2,8 @@ syntax = "proto3";
|
|||
|
||||
package join;
|
||||
|
||||
import "internal/versions/components/components.proto";
|
||||
|
||||
option go_package = "github.com/edgelesssys/constellation/v2/joinservice/joinproto";
|
||||
|
||||
service API {
|
||||
|
@ -42,7 +44,7 @@ message IssueJoinTicketResponse {
|
|||
// kubernetes_version is the Kubernetes version to install on the node.
|
||||
string kubernetes_version = 9;
|
||||
// kubernetes_components is a list of components to install on the node.
|
||||
repeated KubernetesComponent kubernetes_components = 10;
|
||||
repeated components.Component kubernetes_components = 10;
|
||||
}
|
||||
|
||||
message control_plane_cert_or_key {
|
||||
|
@ -64,15 +66,3 @@ message IssueRejoinTicketResponse {
|
|||
// This value is NOT persisted on the state disk.
|
||||
bytes measurement_secret = 2;
|
||||
}
|
||||
|
||||
// Discuss if we want to import the init proto instead of duplicating it
|
||||
message KubernetesComponent {
|
||||
// url to download the component from.
|
||||
string url = 1;
|
||||
// hash of the component.
|
||||
string hash = 2;
|
||||
// install_path is the path to install the component to.
|
||||
string install_path = 3;
|
||||
// extract indicates whether the component is an archive and needs to be extracted.
|
||||
bool extract = 4;
|
||||
}
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue