This is a breaking change affecting how we work with our data mapping plugins.
Previously, we had a single block type inside transcend_data_silo resources that looked like:
plugin_configuration {
enabled = true
type = "DATA_POINT_DISCOVERY"
schedule_frequency_minutes = 1440 # 1 day
schedule_start_at = "2022-09-06T17:51:13.000Z"
schedule_now = false
}This was inflexible for two major reasons: we only allowed one plugin per data silo, and you had to know the values to put in the type field. With this release, we've replaced this block with a separate block configuration for each plugin type, eliminating the need to lookup type enum values, and making our documentation more explicit with what plugin types are available. This also has the benefit of making it easy to have multiple plugins under one data silo, meaning you can tell a silo such as DynamoDB to discover the schema of your tables (schema plugin) as well as to find an overall listing of the DynamoDB tables you have (data silo discovery) and can even have a classifier plugin that examines samples of your database via our sombra agent and finds personal data within your tables.
Here's an example of what the new configuration could look like:
resource "transcend_data_silo" "aws" {
type = "amazonWebServices"
description = "Amazon Web Services (AWS) provides information technology infrastructure services to businesses in the form of web services."
schema_discovery_plugin {
enabled = true
schedule_frequency_minutes = 1440 # 1 day
schedule_start_at = "2022-09-06T17:51:13.000Z"
}
content_classification_plugin {
enabled = true
schedule_frequency_minutes = 1440 # 1 day
schedule_start_at = "2022-09-06T17:51:13.000Z"
}
# ...other fields...
}What's Changed
New Contributors
Full Changelog: v0.9.1...v0.9.2