Skip to content
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

Restrictions #159

Merged
merged 26 commits into from
Mar 12, 2021
Merged

Restrictions #159

merged 26 commits into from
Mar 12, 2021

Conversation

nilmerg
Copy link
Member

@nilmerg nilmerg commented Jan 28, 2021

Adds the following restrictions:

  • icingadb/filter/objects (Applies to all objects)
  • icingadb/filter/hosts (Applies to hosts and services)
  • icingadb/filter/services (Applies only to services)
  • icingadb/blacklist/variables (Hides custom variables)
  • icingadb/protect/variables (Obfuscates custom variables with ***)

Why is icingadb/filter/hosts also to services applied? Because if you can access a host, you might not access all services as a host can exist without any service. A service however can't exist without a host and therefore, if you can't access the host, you can't access its services.

refs Icinga/icingaweb2#3349
refs Icinga/icingaweb2#3550

@nilmerg nilmerg added the enhancement New feature or improvement label Jan 28, 2021
@nilmerg nilmerg self-assigned this Jan 28, 2021
@nilmerg nilmerg force-pushed the feature/restrictions branch 4 times, most recently from f6baa8b to 811002a Compare January 29, 2021 09:45
@nilmerg nilmerg mentioned this pull request Jan 29, 2021
nilmerg added 17 commits March 9, 2021 09:21
Previously, also service comments were counted.
Previously also service comments and downtimes were shown.
Otherwise not all hostgroups are shown if there's a host restriction active
Otherwise not all servicegroups are shown if there's a service restriction active
...and not with as much queries as there are notifications*recipients
@nilmerg nilmerg force-pushed the feature/restrictions branch from 811002a to e9d132a Compare March 9, 2021 08:26
@nilmerg nilmerg force-pushed the feature/restrictions branch from 25e3033 to 6eeaf39 Compare March 9, 2021 11:23
nilmerg added 2 commits March 11, 2021 16:37
This is a preparation for the custom variable restrictions
as they're supposed to be applied on the query.
@nilmerg nilmerg force-pushed the feature/restrictions branch 2 times, most recently from 9d62bac to 0920fbe Compare March 12, 2021 08:09
@nilmerg nilmerg force-pushed the feature/restrictions branch from 3f9a382 to aae4c01 Compare March 12, 2021 10:27
@nilmerg nilmerg merged commit e14cf93 into master Mar 12, 2021
@nilmerg nilmerg deleted the feature/restrictions branch March 12, 2021 10:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or improvement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant