[dev.icinga.com #13125] Import hosts with AWS modul

[icinga-migration]

This issue has been migrated from Redmine: https://dev.icinga.com/issues/13125

Created by stay on 2016-11-10 10:19:05 +00:00

Assignee: (none)
Status: New
Target Version: (none)
Last Update: 2016-12-02 19:59:55 +00:00 (in Redmine)

---

Hi folks,
I´m currently trying to create a import based on the AWS module.
I´ve set up everything as described in the documentation, and after the first source import i can successfully see the EC2 Instances in the preview tab.
My issue is with the sync rule.
I don´t want to sync all instances, therefore I´ve modified the sync rule with a filter expression.
The filter expression is: tags.Application=IIS.
If I try to trigger the sync rule, i´m being told that nothing changed and no host are imported.
The import source does actually not hold the field "tags.Application", but the field "tags", does hold it. As this field is a JSON, I do think my expression in the sync rule should work.
Do I have to create dedicated modifier for the import source? If so what is the best way to do so?
Any help is appreciated.
Cheers!

[icinga-migration]

Updated by mbassett on 2016-12-02 19:59:55 +00:00

You probably want to open this in the director-aws repository here https://github.com/Icinga/icingaweb2-module-aws/issues

I have noticed similar behavior in the sync rule not applying unless the underlying ec2 import source changes. IE, spin a new instance or delete an instance. Then re-run the sync.

Obviously this is only a workaround and I too would like to understand what is broken and how to fix it permanently.

[Thomas-Gelf]

Yep, wrong issue tracker - closing this one