Silent Failure to store with partially identical documents

[ashearin]

During development of document changeset functionality in bomctl, we were attempting to test storing the same document more than once, with only slight differences in the metadata of the document.

So: same sbom id, different metadata contents, same nodelist content.

The storage backend was failing to store said 'revised' documents based on the on conflict, ignore directive in the code, and the only indicator that something failed was the lack of documents in the cache.

Want to use this issue for discussion and tracking, as the maintainers have been made aware of the issue.
Topics:

• Should we be silently failing in these situations?
• How do we handle storing slightly modified documents successfully without duplication of every entry?
  • @jhoward-lm has a working idea for this

[mrsufgi]

@ashearin, I'm getting the same (not in bomctl, but using protobom as BE for storing some sboms). If I store the same sbom twice, it fails silently. im working on a solution and will submit a PR soon.

@puerco @cpanato : this is Ori (formarly @manifestori) from my private account.