Skip to content

Conversation

albertodonato
Copy link
Contributor

@albertodonato albertodonato commented Aug 20, 2025

ENG-5559

what

Add reource for notification report groups.

Note that notification settings for the different transports are not yet
handled. They're present in the resource schema but not passed to the API.
This will be added in a followup branch since this one is already quite large.

why

allow managing notifications via terraform

testing

testing in sandbox, added acceptance tests

docs

updated here

@albertodonato albertodonato requested a review from a team as a code owner August 20, 2025 08:38
[ENG-5559](https://stacklet.atlassian.net/browse/ENG-5559)

### what

Add reource for notification report groups.

Note that notification settings for the different transports are not yet
handled. They're present in the resource schema but not passed to the API.
This will be added in a followup branch since this one is already quite large.

### why

allow managing notifications via terraform

### testing

testing in sandbox, added acceptance tests

### docs

updated here
@albertodonato albertodonato force-pushed the ack/report-group-resource branch from 6478988 to cc37bec Compare August 20, 2025 08:59
Copy link
Contributor

@fwereade fwereade left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I seem to recall that while a Recipient has multiple fields, it requires exactly one of them to be set? and I didn't spot code enforcing that… I guess that's handled on the backend, but it might be worth a mention in the schema docs as well?

Regardless, LGTM, many thanks.

@albertodonato
Copy link
Contributor Author

thanks @fwereade , indeed only one of those fields can be true or not null. I'll add validation for that in the provider separately

@albertodonato albertodonato merged commit 69c1bd8 into main Aug 20, 2025
6 checks passed
@albertodonato albertodonato deleted the ack/report-group-resource branch August 20, 2025 09:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants