In case secret URI was stored in the databag (Peer Relation Data solution before moving to secret labels), don't remove the databag field after the first read, BUT on the first write
This could result in issues in case we do an upgrade (from a version that was retrieving secrets from URI in databag), read our secrets (thus loose the databag internal-field key that was referring to the secret URI) and we do a rollback after.
(NOTE: in case no rollback is applied, all works well.)
github-actions[bot]
commented
5 months ago
In case secret URI was stored in the databag (Peer Relation Data solution before moving to secret labels), don't remove the databag field after the first read, BUT on the first write
This could result in issues in case we do an upgrade (from a version that was retrieving secrets from URI in databag), read our secrets (thus loose the databag
internal-fieldkey that was referring to the secret URI) and we do a rollback after. (NOTE: in case no rollback is applied, all works well.)