Skip to content

Definitions deployment process #98

Description

@obrusvit

The current problems

  • dev definitions are deployed manually to an ad-hoc created directory placed at data.trezor.io. In general, we only want production things in there.
  • prod definitions are also deployed manually
  • created data blob has no version or timestamp in the name

Deployment should be similar to deploying unsigned or signed firmwares at trezor-suite-firmware-releases repository.

Proposed process for dev definitions

  • developer creates a <name>/feature branch and runs do_update.sh
  • PR is created targeting main, a reviewer checks that only data update occurred
  • developer can deploy dev definitions using a CI workflow, similar to tsfr

Proposed process for prod definitions

  • developer creates a release/YY.MM branch and runs do_update.sh
  • signature is produced in a regular Release process
  • developer creates the commit with a newly produced signature using do_sign.sh
  • PR is created targeting main
  • developer can deploy prod definitions using a CI workflow

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

  • Status
    🏃‍♀️ In progress

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions