-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Create plugin dynamo tables #972
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
global secondary index ftw
0505f4e
to
7296a3b
Compare
f454243
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
one comment but LGTM 🔥
}, | ||
{ | ||
name = "is_latest" | ||
type = "S" #terraform only supports String, Number or Binary for primary key attribute |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
how are we planning on storing this? something like true
or false
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, they will be treated as strings with the value "true" or "false".
The data type now unfortunately becomes a part of the business logic.
Relates to #880
Description
Creates tables for
plugin
,plugin-metadata
andplugin-blocked
.The
plugin-blocked
schema follows the spec from the RFC.The
plugin-metadata
table will store the data from different sources such as pypi, github and manifest. The table will follow the schema designed for the plugin table but without the secondary indices. As the records will only have the source data, the attributes in this table will also be only those defined for the source data ie name, version-type, version, type, data, last_updated_timestampThe
plugin
table will store only the aggregated plugin data. The schema follows the spec from the RFC with the change that the range key is now the version of the plugin. Thetype
identifier is no longer needed, as all the records in this table are oftype=AGGREGATE
. This will also result in the type attribute not being stored in this table.