-
Notifications
You must be signed in to change notification settings - Fork 3
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 Security Rule Options #251
Conversation
Openshift URLs for the PR Deployment: |
database/src/migrations/20240808000000_biohub_security_rules.ts
Outdated
Show resolved
Hide resolved
database/src/migrations/20240808000000_biohub_security_rules.ts
Outdated
Show resolved
Hide resolved
@AMEIJER1 Let me know what you think: it seems complex to have separate telemetry/data/dna/etc. rules for each species. It will be much easier to manage security if we just have one rule per species/category, like: Caribou government interest, caribou persecution and harm, grizzly bear persecution and harm, rattlesnake persecution and harm. If we ever need to remove rules after a certain amount of time, we can do things like: remove "caribou" rule where data type = telemetry. A bit of a 180 on our last conversation but I don't think the highly specific rules are sustainable. |
database/src/migrations/20240808000000_biohub_security_rules.ts
Outdated
Show resolved
Hide resolved
Quality Gate passedIssues Measures |
Openshift URLs for the PR Deployment: |
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.
LGTM
Links to Jira Tickets
Description of Changes