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
|`blob_storage_backups.backup_name`| The name of the backup, which must be unique across blob storage backups. | Yes | n/a |
175
152
|`blob_storage_backups.retention_period`| How long the backed up data will be retained for, which should be in `ISO 8601` duration format. This must be specified in days, and can be up to 7 days unless `use_extended_retention` is on. [See the following link for more information about the format](https://en.wikipedia.org/wiki/ISO_8601#Durations). | Yes | n/a |
176
153
|`blob_storage_backups.backup_intervals`| A list of intervals at which backups should be taken, which should be in `ISO 8601` duration format. [See the following link for the possible values](https://en.wikipedia.org/wiki/ISO_8601#Time_intervals). | Yes | n/a |
177
-
|`blob_storage_backups.backup_policy_naming_template`| Naming template allows existing teams to preserve pre-existing blob policy names while enabling consistent naming.| No | {resource_abbreviation}-blob-{backup_name} |
178
-
|`blob_storage_backups.backup_instance_naming_template`| Naming template allows existing teams to preserve pre-existing blob instance names while enabling consistent naming.| No | {resource_abbreviation}-blob-{backup_name} |
154
+
|`blob_storage_backups.backup_policy_naming_template`| Naming template used to construct the blob backup instance name. The following placeholders are supported and will be replaced by the module: `{resource_abbreviation}` → `bkpol`, `{resource_type}` → `blob`, `{backup_name}` → value of `blob_storage_backups.backup_name`| No | {resource_abbreviation}-{resource_type}-{backup_name} |
155
+
|`blob_storage_backups.backup_instance_naming_template`| Naming template used to construct the blob backup instance name. The following placeholders are supported and will be replaced by the module: `{resource_abbreviation}` → `bkinst`, `{resource_type}` → `blob`, `{backup_name}` → value of `blob_storage_backups.backup_name`| No | {resource_abbreviation}-{resource_type}-{backup_name} |
179
156
|`blob_storage_backups.time_zone`| The time zone to apply to the backup policy schedule (eg. Europe/London). If not specified, Azure’s default time zone behaviour is used. | No | n/a |
180
157
|`blob_storage_backups.enable_daily_retention_rule`| Enables an additional daily retention rule on the backup policy. This is optional and intended for scenarios that require explicit daily retention behaviour beyond the default policy configuration. | No | false |
181
158
|`managed_disk_backups`| A map of managed disk backups that should be created. For each backup the following values should be provided: `managed_disk_id`, `backup_name` and `retention_period`. When no value is provided then no backups are created. | No | n/a |
182
159
|`managed_disk_backups.managed_disk_id`| The id of the managed disk that should be backed up. | Yes | n/a |
183
160
|`managed_disk_backups.backup_name`| The name of the backup, which must be unique across managed disk backups. | Yes | n/a |
184
161
|`managed_disk_backups.retention_period`| How long the backed up data will be retained for, which should be in `ISO 8601` duration format. This must be specified in days, and can be up to 7 days unless `use_extended_retention` is on. [See the following link for more information about the format](https://en.wikipedia.org/wiki/ISO_8601#Durations). | Yes | n/a |
185
162
|`managed_disk_backups.backup_intervals`| A list of intervals at which backups should be taken, which should be in `ISO 8601` duration format. [See the following link for the possible values](https://en.wikipedia.org/wiki/ISO_8601#Time_intervals). | Yes | n/a |
186
-
|`managed_disk_backup.backup_policy_naming_template`| Naming template allows existing teams to preserve pre-existing disk policy names while enabling consistent naming.| No | {resource_abbreviation}-disk-{backup_name} |
187
-
|`managed_disk_backup.backup_instance_naming_template`| Naming template allows existing teams to preserve pre-existing disk instance names while enabling consistent naming.| No | {resource_abbreviation}-disk-{backup_name} |
163
+
|`managed_disk_backup.backup_policy_naming_template`| Naming template used to construct the disk backup instance name. The following placeholders are supported and will be replaced by the module: `{resource_abbreviation}` → `bkpol`, `{resource_type}` → `disk`, `{backup_name}` → value of `managed_disk_backup.backup_name`| No | {resource_abbreviation}-{resource_type}-{backup_name} |
164
+
|`managed_disk_backup.backup_instance_naming_template`| Naming template used to construct the disk backup instance name. The following placeholders are supported and will be replaced by the module: `{resource_abbreviation}` → `bkinst`, `{resource_type}` → `disk`, `{backup_name}` → value of `managed_disk_backup.backup_name`| No | {resource_abbreviation}-{resource_type}-{backup_name} |
188
165
|`postgresql_flexible_server_backups`| A map of postgresql flexible server backups that should be created. For each backup the following values should be provided: `backup_name`, `server_id`, `server_resource_group_id`, `retention_period` and `backup_intervals`. When no value is provided then no backups are created. | No | n/a |
189
166
|`postgresql_flexible_server_backups.backup_name`| The name of the backup, which must be unique across postgresql flexible server backups. | Yes | n/a |
190
167
|`postgresql_flexible_server_backups.server_id`| The id of the postgresql flexible server that should be backed up. | Yes | n/a |
191
168
|`postgresql_flexible_server_backups.server_resource_group_id`| The id of the resource group which the postgresql flexible server resides in. | Yes | n/a |
192
169
|`postgresql_flexible_server_backups.retention_period`| How long the backed up data will be retained for, which should be in `ISO 8601` duration format. This must be specified in days, and can be up to 7 days unless `use_extended_retention` is on. [See the following link for more information about the format](https://en.wikipedia.org/wiki/ISO_8601#Durations). | Yes | n/a |
193
170
|`postgresql_flexible_server_backups.backup_intervals`| A list of intervals at which backups should be taken, which should be in `ISO 8601` duration format. [See the following link for the possible values](https://en.wikipedia.org/wiki/ISO_8601#Time_intervals). | Yes | n/a |
194
-
|`postgresql_flexible_server_backup.backup_policy_naming_template`| Naming template allows existing teams to preserve pre-existing pgflex policy names while enabling consistent naming.| No | {resource_abbreviation}-pgflex-{backup_name} |
195
-
|`postgresql_flexible_server_backup.backup_instance_naming_template`| Naming template allows existing teams to preserve pre-existing pgflex instance names while enabling consistent naming.| No | {resource_abbreviation}-pgflex-{backup_name} |
171
+
|`postgresql_flexible_server_backup.backup_policy_naming_template`| Naming template used to construct the pgflex server backup instance name. The following placeholders are supported and will be replaced by the module: `{resource_abbreviation}` → `bkpol`, `{resource_type}` → `pgflex`, `{backup_name}` → value of `postgresql_flexible_server_backup.backup_name`| No | {resource_abbreviation}-{resource_type}-{backup_name} |
172
+
|`postgresql_flexible_server_backup.backup_instance_naming_template`| Naming template used to construct the pgflex server backup instance name. The following placeholders are supported and will be replaced by the module: `{resource_abbreviation}` → `bkinst`, `{resource_type}` → `pgflex`, `{backup_name}` → value of `postgresql_flexible_server_backup.backup_name`| No | {resource_abbreviation}-{resource_type}-{backup_name} |
0 commit comments