-
Notifications
You must be signed in to change notification settings - Fork 20
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
Add connection dimension. Add variable list of tag dimensions (default Owner). #112
Conversation
controls/lambda.sp
Outdated
end as reason, | ||
region, | ||
account_id, | ||
_ctx ->> 'connection_name' as connection |
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.
I think if we re going to add an ability to specify additional dimensions anyway, we should not hardcode _ctx ->> 'connection_name'
as a dimension. The control title already get truncated and this will make it worse. Also, _ctx ->> 'connection_name'
is about the only "custom" dimension that you could add anyway right now, since the other common columns are already included.
@@ -7,6 +7,20 @@ locals { | |||
} | |||
} | |||
|
|||
variable "tag_dimensions" { | |||
type = list(string) | |||
description = "A list of tags to add as dimensions to each control." |
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.
Maybe the description should state the caveats:
- The added dimension column must appear in every control query ( i assume we are generalizing this?)
- The added dimension column must be unique in every control query (when joining tables)
…sions SQL to include qualifier support when required.
Co-authored-by: misraved <[email protected]>
…lect the common dimensions
No description provided.