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
It was not possible to use an instance of gcstorageretriever.Retriever{} since it is only able to get the file on the initial bootstrap of go-feature-flag instance. After feature flag client is up and running, the internal flags cache is no longer updated when gcstorageretriever is used.
Expected Behavior
gcstorageretriever.Retriever{} should be able to the flags when the file stored in google cloud storage changes.
Observed behavior
It was not possible to use an instance of
gcstorageretriever.Retriever{}
since it is only able to get the file on the initial bootstrap of go-feature-flag instance. After feature flag client is up and running, the internal flags cache is no longer updated when gcstorageretriever is used.Expected Behavior
gcstorageretriever.Retriever{}
should be able to the flags when the file stored in google cloud storage changes.Steps to reproduce
Using the following code(just an exaple):
After the bootstrap, we are able to get current flags data, for example using the following func:
But, if the file is updated in google cloud storage, go-feature-flag is not able to retrieve the current config.
Moreover, We can see several log traces that refer to the following line of code(saying file not found)
The text was updated successfully, but these errors were encountered: