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
Right now when we save data into Datastore we don't have any way to distinguish which Turbinia instance is saving the entities, which means that we can't have more than one Turbinia instance per cloud project without mixing the task status results together. We should add a new 'instance' (or something similar) as part of the entity key to help disambiguate. We could potentially use the config.PSQ_TOPIC variable here as this should already be unique.
The text was updated successfully, but these errors were encountered:
Instance is now a datastore TurbiniaTask entity attribute, but I'm keeping this open to add this as a namespace, which is a Datastore concept for multi-tenancy, rather than as an attribute.
This is quite a low priority given that everything works just fine with multiple instances in the same project. We could still do this to be more Datastore idiomatic, but it's really not needed. Closing this out.
Right now when we save data into Datastore we don't have any way to distinguish which Turbinia instance is saving the entities, which means that we can't have more than one Turbinia instance per cloud project without mixing the task status results together. We should add a new 'instance' (or something similar) as part of the entity key to help disambiguate. We could potentially use the config.PSQ_TOPIC variable here as this should already be unique.
The text was updated successfully, but these errors were encountered: