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

Notifications Sync Rule not working with assign_filter #2142

Closed
EmmaTinten opened this issue Jun 8, 2020 · 2 comments
Closed

Notifications Sync Rule not working with assign_filter #2142

EmmaTinten opened this issue Jun 8, 2020 · 2 comments
Assignees
Labels
Milestone

Comments

@EmmaTinten
Copy link

EmmaTinten commented Jun 8, 2020

Expected Behavior

I want to create a sync rule to import notifications using an assign_filter rule for host and servicegroups.
The sync rule should create the corresponding notifications.

Current Behavior

Configuring the sync rule property for "assign_filter" results in the following message in the preview: "I can only assign for applied objects or objects with native support for assigments, got object".

Steps to Reproduce (for bugs)

  1. Create a import source to import groups (groupnames, mailadress).
  2. Create a sync rule using destinations for object_name, import and apply_to (service).
  3. Add the missing property "assign_filter" for the sync rule. Use any expression you wish.

Your Environment

  • Director version (System - About): 1.7.2
  • Icinga Web 2 version and modules (System - About): 2.7.3
  • Icinga 2 version (icinga2 --version): r2.11.3-1
  • Operating System and version: Debian GNU/Linux 10 (buster)
  • Webserver, PHP versions:
    • apache2 2.4.38-3+deb10u3
    • php 2:7.3+69
@EmmaTinten EmmaTinten changed the title Notifications Sync Rule not working with assign_to Notifications Sync Rule not working with assign_filter Jun 8, 2020
@cmusinsky
Copy link

Hi @EmmaTinten,

I ran into a couple similar issues when trying to import Notifications via sync. I outlined what I did to get them working here: #2128 (comment)

Hope it helps!

Thomas-Gelf added a commit that referenced this issue Nov 2, 2022
Complain about missing object_type, if assign-related properties cannot be
set because of that reason

refs #2142
@Thomas-Gelf
Copy link
Contributor

The error message is misleading, 63d76ab addresses this

Thomas-Gelf added a commit that referenced this issue Nov 3, 2022
One more improved exception

refs #2142
@Thomas-Gelf Thomas-Gelf self-assigned this Nov 3, 2022
@Thomas-Gelf Thomas-Gelf added the bug label Nov 3, 2022
@Thomas-Gelf Thomas-Gelf added this to the v1.10.2 milestone Nov 3, 2022
Thomas-Gelf added a commit that referenced this issue Nov 3, 2022
Complain about missing object_type, if assign-related properties cannot be
set because of that reason

refs #2142
Thomas-Gelf added a commit that referenced this issue Nov 3, 2022
One more improved exception

refs #2142
Thomas-Gelf added a commit that referenced this issue Nov 3, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants