Add condition for getting max revision id from store

[pangorgo]

About the changes

In our staging setup, we create ad-hoc environments and import Unleash state from production. After unleash is deployed on such environment, the import job kicks in and feeds Unleash instance with feature flags from production.

Between Unleash being up and running and the import job running, some applications start polling Unleash. They get an empty feature toggle list with meta.revisionId=0. Then apps use this as part of eTag header in subsequent requests. Even though after import Unleash server finally has toggles to serve, it doesn't because it calculates max revision id based on toggle updates (not null feature_name column in query) or SEGMENT_UPDATED.

This change adds an extra condition to query so feature toggles import is considered something that should invalidate the cache.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
unleash-docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 29, 2023 1:04pm
unleash-monorepo-frontend	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Sep 29, 2023 1:04pm

[vercel]

@pangorgo is attempting to deploy a commit to the unleash-team Team on Vercel.

A member of the Team first needs to authorize it.

[pangorgo]

@sjaanus @chriswk @ivarconr is there anything I can do to get this change reviewed and merged? Are any further explanations required?

[ivarconr]

@sjaanus @chriswk @ivarconr is there anything I can do to get this change reviewed and merged? Are any further explanations required?

This works. But you should consider using the new import/export, which will not have these issues.

[ivarconr]

State service, which creates these event types, are deprecated and will go away in Unleash v6. We need to keep this until then.