tl_jacob
Best practices for managing schedules across environments
Let's say we have a set flows that we'd like to run on a schedule in our production environment, but want those flows' schedules disabled in development environments. What are the best practices around marking a schedule as enabled/disabled in different environments?
1 replies
Ignoring .venv during script metadata generation
@rubenf I am using
uv for local script development, which creates a .venv directory within the script directory. I noticed that script generate-metadata was taking a long time > 40sec for a single script and was able to determine that the bottleneck is findGlobalDeps iterating over all the files in the .venv directory when trying to find a lockfile candidate.
I already have a requirements.txt right next to the script. Is there a way to either:
1. have script generate-metadata ignore the .venv directory OR
2. point script generate-meatdata right at the requirements.txt?
For #1, adding --excludes '**/.venv/** doesn't work4 replies
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?3 replies
