Notification Settings
This page explores adding group notification settings to loop in reviewer during Resourcely guardrails violations.
Last updated
This page explores adding group notification settings to loop in reviewer during Resourcely guardrails violations.
Last updated
A Group is a set of stakeholders for guardrails that can be looped in during changes. Groups contain the following fields:
Name
Contact Info (Email)
List of Reviewers (Github, Gitlab)
A reviewer is a person or team who will be set to review a Pull Request (PR). Resourcely automatically assigns a reviewer defined in a group to review an infrastructure resource before it is provisioned.
Letβs get started with configuring your notification settings within Resourcely. This step entails:
Now let's create a Group notification settings within our tenant. You can create a notification settings by pressing the Add notification group
button. Here you will need to provide the name of your Group (Example: Security, Development, Compliance, etc.). You can provide a name and email for your group.
Note: To begin onboarding, only one group is essential. However, you have the flexibility to add more groups later.
Next, you must add a Reviewer to the group. You can add a reviewer by pressing the Add reviewer button. You must then select a provider (GitHub or GitLab) and type in the Reviewer's username.
If using GitHub as a provider, you must add a GitHub team as a reviewer instead of individual users. For GitLab, you must add the exact username.
Note: Only one reviewer is required to onboard. You can add more later as needed.
Once reviewers have been assigned to a group you, you can choose to set the group as default reviewer when a guardrail violation is triggered from change management. Now you can press the Save notification group button
You can create more Group notification settings if needed. Next is to configure Source Code Management integrations.