From 6a82e318367859e14d7a54ff5fb7cfef1c4fd4a4 Mon Sep 17 00:00:00 2001 From: Erikson Tung Date: Mon, 27 Jul 2020 18:16:56 -0700 Subject: [PATCH] pubsys: minor comment changes in Infra.toml * Corrects the env variable to override for changing the `repo` pubsys reads from. Should be `PUBLISH_REPO` and not `REPO`. * Adds a similar comment for changing the `signing-key` used by pubsys. --- tools/pubsys/Infra.toml.example | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/tools/pubsys/Infra.toml.example b/tools/pubsys/Infra.toml.example index 2bb5276fd55..b60dc11ee01 100644 --- a/tools/pubsys/Infra.toml.example +++ b/tools/pubsys/Infra.toml.example @@ -9,6 +9,8 @@ root_role_path = "/home/user/root.json" # as part of the initial setup of your TUF roles. pubsys assumes a single # publication key that lives in the snapshot, targets, and timestamp roles. # Here you specify where that key lives so we can sign the created repo. +# You can specify multiple keys, if you like, and select one by name: +# cargo make repo -e PUBLISH_KEY=mysigningkey # (Don't keep your keys in the repo!) # You can keep your private key in a file or an SSM parameter; pick one: # (Need inline table syntax until this is fixed: https://github.com/alexcrichton/toml-rs/issues/225) @@ -16,7 +18,7 @@ signing_keys = { default = { file = { path = "/home/user/key.pem" } } } # signing_keys = { default = { ssm = { parameter = "/my/parameter" } } } # You can have any number of repos defined and build a specific one by running like this: -# cargo make repo -e REPO=myrepo +# cargo make repo -e PUBLISH_REPO=myrepo # If the URLs are uncommented, they will be pulled and used as a starting # point, and your images (and related files) will be added as a new update in # the created repo. Otherwise, we build a new repo from scratch.