Skip to content

fix: add missing deploy key fields to DynamoDB schema (#514)#526

Open
dennismdejong wants to merge 1 commit into
PacoVK:mainfrom
dennismdejong:fix/upstream-514-deploykey-missing-fields
Open

fix: add missing deploy key fields to DynamoDB schema (#514)#526
dennismdejong wants to merge 1 commit into
PacoVK:mainfrom
dennismdejong:fix/upstream-514-deploykey-missing-fields

Conversation

@dennismdejong

Copy link
Copy Markdown

Fixes #514

The DeployKey table schema in DynamoDB was only persisting 3 of 9 fields: id, key, and createdAt. Fields resourceType, scope, source, namespace, provider, name, and type were silently dropped because they were not registered in the enhanced client schema builder. Also added missing setters to DeployKey model for deserialization.

The DeployKey table schema in DynamoDB was only persisting 3 of 9 fields:
id, key, and createdAt. Fields resourceType, scope, source, namespace,
provider, name, and type were silently dropped because they were not
registered in the enhanced client schema builder. Also added missing
setters to DeployKey model for deserialization.

Fixes PacoVK#514
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Deploy Keys Missing Fields

1 participant