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
The current problems
data.trezor.io. In general, we only want production things in there.Deployment should be similar to deploying unsigned or signed firmwares at
trezor-suite-firmware-releasesrepository.Proposed process for dev definitions
<name>/featurebranch and runsdo_update.shmain, a reviewer checks that only data update occurredtsfrProposed process for prod definitions
release/YY.MMbranch and runsdo_update.shdo_sign.shmain