dc
a07728be2b
The published sites get the same key pair on every deploy, committed as sas/mocks/mock-licence.json (site_id 123, the mock estate's SYSSITE) rather than generated in the pipeline. The pair sits outside the deployed sync folder, so the CI estate stays unlicensed and the Cypress specs keep exercising the free tier. The Sites job copies the pair into the drive before the snapshot and refuses a pair whose two values are identical, which is how the app spots an HTTP-format key it cannot decrypt in a secure context. The pair trips the generic-api-key scanner, so .gitleaksignore carries the two fingerprints.
6 lines
277 B
Plaintext
6 lines
277 B
Plaintext
# sas/mocks/mock-licence.json holds a licence key pair for the mock estate: the
|
|
# activation key is RSA key material the browser demo decrypts with, not a
|
|
# credential for any service.
|
|
sas/mocks/mock-licence.json:generic-api-key:2
|
|
sas/mocks/mock-licence.json:generic-api-key:3
|