-
Notifications
You must be signed in to change notification settings - Fork 18
strip down rule_metadata #4056
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
base: importer-rework
Are you sure you want to change the base?
strip down rule_metadata #4056
Conversation
…firewall-orchestrator into feature/rule-metadata-rework-4031
…firewall-orchestrator into feature/rule-metadata-rework-4031
abarz722
left a comment
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.
Looks reasonable
| CREATE OR REPLACE VIEW v_rule_with_rule_owner AS | ||
| SELECT r.rule_id, ow.id as owner_id, ow.name as owner_name, 'rule' AS matches, | ||
| ow.recert_interval, met.rule_last_certified, met.rule_last_certifier | ||
| ow.recert_interval, max(rec.recert_date) AS rule_last_certified |
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.
Hope we will not run into performance issues with growing number of recertifications. (Then we maybe have to reintroduce rule_last_certified field)
|



No description provided.