constellation/bazel/ci/proto_targets.bzl

"""Proto targets"""

def proto_targets():
    return [
        "//joinservice/joinproto:write_generated_protos",
        "//bootstrapper/initproto:write_generated_protos",
        "//debugd/service:write_generated_protos",
        "//disk-mapper/recoverproto:write_generated_protos",
        "//keyservice/keyserviceproto:write_generated_protos",
        "//internal/versions/components:write_generated_protos",
        "//upgrade-agent/upgradeproto:write_generated_protos",
        "//verify/verifyproto:write_generated_protos",
    ]
bazel: add protoc codegen to //:generate target (#1554) Signed-off-by: Paul Meyer <49727155+katexochen@users.noreply.github.com> 2023-03-30 08:47:29 -04:00			`"""Proto targets"""`

			`def proto_targets():`
			`return [`
			`"//joinservice/joinproto:write_generated_protos",`
			`"//bootstrapper/initproto:write_generated_protos",`
			`"//debugd/service:write_generated_protos",`
			`"//disk-mapper/recoverproto:write_generated_protos",`
			`"//keyservice/keyserviceproto:write_generated_protos",`
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. 2023-12-11 08:08:55 +01:00			`"//internal/versions/components:write_generated_protos",`
bazel: add protoc codegen to //:generate target (#1554) Signed-off-by: Paul Meyer <49727155+katexochen@users.noreply.github.com> 2023-03-30 08:47:29 -04:00			`"//upgrade-agent/upgradeproto:write_generated_protos",`
			`"//verify/verifyproto:write_generated_protos",`
			`]`