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
Describe the bug
Currently hasSourceAt uses metadata timestamp which is set when the attestation is created. This needs to be changed to Meta-Updated timestamp which is when Clearly Defined last scanned for this information.
The current timestamp causes the hasSourceAt to node to be re-created because of the KnownSince field changing. More accurately, this should only be re-created when clearly defined has re-scanned on its own service.
Expected behavior
Not recreate hasSourceAt nodes when a the scanned timestamp from clearly defined has not changed during the ceritifer run.
GUAC version
v0.8.8
The text was updated successfully, but these errors were encountered:
Describe the bug
Currently hasSourceAt uses metadata timestamp which is set when the attestation is created. This needs to be changed to Meta-Updated timestamp which is when Clearly Defined last scanned for this information.
The current timestamp causes the hasSourceAt to node to be re-created because of the
KnownSince
field changing. More accurately, this should only be re-created when clearly defined has re-scanned on its own service.Expected behavior
Not recreate hasSourceAt nodes when a the scanned timestamp from clearly defined has not changed during the ceritifer run.
GUAC version
v0.8.8
The text was updated successfully, but these errors were encountered: