Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

pubsys: minor comment changes in Infra.toml.example #1004

Merged
merged 1 commit into from
Jul 28, 2020
Merged

pubsys: minor comment changes in Infra.toml.example #1004

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 3 additions & 1 deletion tools/pubsys/Infra.toml.example
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,14 +9,16 @@ 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)
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.
Expand Down