Description
Problem:
According to our documentation it should always be possible to add new attributes to our model without issue: https://docs.aws.amazon.com/dynamodb-encryption-client/latest/devguide/data-model.html#add-attribute
However, if you start with data encrypted using
actions = AttributeActions(
default_action=CryptoAction.DO_NOTHING
)
And update to using
actions = AttributeActions(
default_action=CryptoAction.DO_NOTHING, attribute_actions={"someNewField": CryptoAction.ENCRYPT_AND_SIGN}
)
You run into issues. This is because data under the first model doesn't have a material description or signature written with it. Once the model is updated to include an action other than DO_NOTHING
, it always expects there to be a material description and signature, even if the record it's attempting to decrypt doesn't include someNewField
yet.
Solution:
We should probably update the logic here to also pass through if the item under decrypt specifically doesn't have attributes where encryption or signing is needed, even if the attributeActions includes an encrypt or sign action for a non-present field.
aws-dynamodb-encryption-python/src/dynamodb_encryption_sdk/encrypted/item.py
Lines 176 to 178 in 25c7c3d
aws-dynamodb-encryption-python/src/dynamodb_encryption_sdk/structures.py
Lines 137 to 148 in 25c7c3d