When specifying an org_id as an attribute for a RuleGroup resource, it is ignored and the rule group is always created in the org with id 1. Example (leaving the rule definitions empty for brevity):
When I run this, the folder will get created in the correct org (id=3), but no rule groups show up even though pulumi thinks it has created them. If I look at the outputs for the RuleGroup resource, I see the "orgId": "1", and when I re-run the pulumi up command, the diff shows:
And then don't pass org_id in the RuleGroup args, things work as expected and the alerts get created in the correct org. However I get these deprecation warnings:
warning: org_id is deprecated: Use the `org_id` attributes on resources instead.
warning: org_id is deprecated: Use the `org_id` attributes on resources instead.
warning: provider config warning: Use the `org_id` attributes on resources instead.
warning: provider config warning: Use the `org_id` attributes on resources instead.
Expected Behavior:
I should be able to set org_id as a kwarg when creating a RuleGroup (like the deprecation warning suggests) and have the rules get created in the correct org
When specifying an
org_id
as an attribute for aRuleGroup
resource, it is ignored and the rule group is always created in the org with id1
. Example (leaving the rule definitions empty for brevity):When I run this, the folder will get created in the correct org (id=3), but no rule groups show up even though pulumi thinks it has created them. If I look at the outputs for the RuleGroup resource, I see the
"orgId": "1"
, and when I re-run the pulumi up command, the diff shows:I have to hardcode the
folder_uid
to an id of a folder I created manually in orgId 1, but then I can see that alerts do actually get created there.If I change the provider to use the
org_id
attribute as such:And then don't pass
org_id
in the RuleGroup args, things work as expected and the alerts get created in the correct org. However I get these deprecation warnings:Expected Behavior: I should be able to set
org_id
as a kwarg when creating aRuleGroup
(like the deprecation warning suggests) and have the rules get created in the correct org