You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If we ever leak license signing keys, we want to be able to generate new ones. But, we can't start using a new key until after the public key has been added to a released version of Coder. So, we can't just take the latest key, we need to be configured.
AC:
export LICENSOR_KEY_BUCKET to a Google Cloud Bucket containing multiple keys
export LICENSOR_KEY_ID to the older key in the bucket
start the server
generate a license
verify the license uses the correct key
stop the server and change LICENSOR_KEY_ID to another key in the bucket
start the server
generate a license
verify the license uses the correct key
Note: automated unit testing is generally not required for this repo
The text was updated successfully, but these errors were encountered:
Problem:
If we ever leak license signing keys, we want to be able to generate new ones. But, we can't start using a new key until after the public key has been added to a released version of Coder. So, we can't just take the latest key, we need to be configured.
AC:
LICENSOR_KEY_BUCKET
to a Google Cloud Bucket containing multiple keysLICENSOR_KEY_ID
to the older key in the bucketLICENSOR_KEY_ID
to another key in the bucketNote: automated unit testing is generally not required for this repo
The text was updated successfully, but these errors were encountered: