Skip to content

bug(policies): Dependent tables aren't correctly documented if used in views #10249

@disq

Description

@disq

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

If a policy is creating and using a view, the tables used in the view aren't documented in the policies section on the website.

Current docs: https://www.cloudquery.io/docs/plugins/sources/aws/policies

Some of the AWS policies seem to create and use a view_aws_log_metric_filter_and_alarm view, which depend on a quite a few tables, but some of them aren't really used on any other query so aren't included in the final list in the docs.aws_cloudwatch_alarms and aws_sns_subscriptions are missing (there might be more)

Expected Behavior

Docs should contain all required tables for the specified policy to work.

CloudQuery (redacted) config

Steps To Reproduce

CloudQuery (redacted) logs

CloudQuery version

latest main

Additional Context

No response

Pull request (optional)

  • I can submit a pull request

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions