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
bring pattern matching feature to exemptions (#1008)
* added subscription pattern matching to exemptions
* undo formatting to try and get a cleaner PR
* add documentation
* update doc with tip
---------
Co-authored-by: Sean Krall <[email protected]>
Copy file name to clipboardExpand all lines: Docs/policy-exemptions.md
+24-1Lines changed: 24 additions & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -168,7 +168,30 @@ It is unchanged from previous versions.
168
168
In CSV files, the `scope` column is still supported for backward compatibility. We recommend using the `scopes` column for all new exemptions. `scopes` is a list of ampersand `&` separated strings.
169
169
170
170
In JSON files, `scope` is a string and `scopes` is an array of strings.
171
-
171
+
172
+
### Pattern Matching
173
+
174
+
You can define a pattern to match on subscriptions or resource groups for scopes. This allows an exemption to add matched subscriptions or resource group names to the exempted scope. It is not dynamic i.e. if you add subscriptions or resource groups later and want to include them you would have to run the plan again.
> If you want to match against a subscriptions name, rather than it's ID, you need to use the `subscriptionsPattern` to designate the name with the wildcards.
194
+
172
195
## Combining Policy Definitions at multiple Scopes
173
196
174
197
When using **Option A** or **Option C** and/or `scopes`, EPAC needs to generate concatenated values for `name`, `displayName`, and `description` to ensure uniqueness and readability.
0 commit comments