You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+3-13Lines changed: 3 additions & 13 deletions
Original file line number
Diff line number
Diff line change
@@ -76,7 +76,7 @@ resources:
76
76
relayers:
77
77
relayer-1:
78
78
name: 'Test Relayer 1'
79
-
network: 'goerli'
79
+
network: 'sepolia'
80
80
min-balance: 1000
81
81
policy: ${self:resources.policies.policy-1}
82
82
api-keys:
@@ -99,16 +99,14 @@ A list of properties that support direct referencing:
99
99
- `action-trigger`may reference an `actionid` in Monitor
100
100
- `action-condition`may reference an `actionId` in Monitor
101
101
- `address-from-relayer`may reference a `relayerId` in Relayer
102
-
- `notification-ids`may reference multiple `notificationId` in Category
103
102
- `notify-config.channels`may reference multiple `notificationId` in Monitor
104
-
- `notify-config.category`may reference a `categoryId` in Monitor
105
103
- `contracts`may be used over `addresses` and reference multiple `contractId` in Monitor
106
104
The following is an example of how a direct reference to a Defender contract and relayer can be used in monitor and action respectively:
107
105
108
106
```yaml
109
107
...
110
108
contracts:
111
-
contract-1: 'goerli-0xd70d6A0480420b4C788AF91d0E1b0ca6141A9De8' # contractId of an existing resource in Defender
109
+
contract-1: 'sepolia-0x62034459131329bE4349A9cc322B03c63806Aa11' # contractId of an existing resource in Defender
112
110
relayers:
113
111
relayer-2: 'bcb659c6-7e11-4d37-a15b-0fa9f3d3442c' # relayerId of an existing relayer in Defender
114
112
actions:
@@ -124,7 +122,7 @@ monitors:
124
122
block-example:
125
123
name: 'Block Example'
126
124
type: 'BLOCK'
127
-
network: 'goerli'
125
+
network: 'sepolia'
128
126
risk-category: 'TECHNICAL'
129
127
# optional - either contracts OR addresses should be defined
130
128
contracts:
@@ -209,14 +207,6 @@ More information can be found on our documentation page [here](https://docs.open
209
207
210
208
## Caveats
211
209
212
-
Note that when setting up the notification configuration for a monitor, the `channels` property will always be prioritised over `category`. A notification category can only be associated to a monitor with no linked notification channels. This means that the `channels` property should be assigned the value `[]` in order to prioritise the `category` property.
213
-
214
-
```yaml
215
-
notify-config:
216
-
channels: [] # assign channels as empty list if you wish to use a category
0 commit comments