Deployment and license key
Hello! I have some questions about best practices around provisioning instances with license keys.
Context:
We currently are storing a license key in a secret store and injecting it into the
instance_settings.yaml an pushing those settings to our instance (running in ECS) at deploy-time. However, the license key in our secret manager goes out of sync with the one on the instance after the automatic daily key renewal. The approach we are considering is to
1. create an instance_settings.yaml using the license key in our secret store. This license key may be expired
2. pull down the latest settings from our instance and if a license key exists in those remote settings, overwrite the one stored in our local settings.
3. push the merged settings file to the instance
The problem here is the first deployment will likely have an expired key, which leads me to question 1 below.
Questions:
1. Is there a way to programatically refresh a license key? I've tried hitting the renew_license_key endpoint, but having trouble with the auth (and it looks like the implementation is closed source).
2. What is the recommended way of provisioning an instance with a license key at deploy-time?GitHub
windmill/backend/windmill-api/src/settings.rs at 56b417c669172c38bb...
Open-source developer platform to power your entire infra and turn scripts into webhooks, workflows and UIs. Fastest workflow engine (13x vs Airflow). Open-source alternative to Retool and Temporal...
1 Reply
the license key refresh automatically
you can set it in the UI directly, and the key will refresh every day