Kim Gustyr

Related to private-cloud work: - https://github.com/Flagsmith/flagsmith-saml/issues/43 - https://github.com/Flagsmith/flagsmith-auth-controller/issues/12 - https://github.com/Flagsmith/flagsmith-rbac/issues/20

More context for https://github.com/Flagsmith/flagsmith/issues/3718#issuecomment-2161033501: Having merged the work related to E2E, and significantly reducing Depot costs, we still have workflows that duplicate each other, specifically the private cloud image build...

Do we limit installations and how (e.g. keep track of installation IDs)? > this file can be passed in with different methods (ENV var, attached volume etc) Most obviously, a...

Trying to solve the same problems, we've had some success with rogisolorzano/github-runner-ec2-start and rogisolorzano/github-runner-ec2-stop GH actions to spin up our own Graviton EC2 runners. We tried to spin up OrbStack...

Hi @plumdog and thanks for the very valuable feedback! The PR essentially solves #126 – Flagsmith is still, and will be, able to leverage InfluxDB backend for analytics, but we...

It's worth mentioning that `rye test` already integrates autosync, but it does regenerate the lock, which is not the desirable behaviour.

> it does regenerate the lock, which is not the desirable behaviour After some research, I found that autosync invokes sync with `update_all == false`, which prompts both `pip-sync` and...

@mitsuhiko @charliermarsh Let me know if you want me to rebase my PR(s) so we can close this?

Hello @a-khalilov! We bumped a bunch of dependencies, including `flat`, in our [fork](https://github.com/Flagsmith/serverless-plugin-canary-deployments) and published it to npm. You can try `npm i @flagsmith/serverless-plugin-canary-deployments` and tell us what you think!

For consistency's sake, the feature health automatic tags are managed in the backend. It shouldn't be a problem to add default tags to existing projects retroactively in the backend either.