Repository navigation
feat: make the blob change feed configurable on storage_account_public (AB#9281) - #461
Merged
Merged
Conversation
…c (AB#9281) Azure keeps the change feed on for as long as an object replication policy uses the account as its source, and rejects any update that turns it off. The module never set change_feed_enabled, so the provider sent its false default and every apply on such an account failed with InvalidRequestPropertyValue: The value 'False' is not allowed for property Change Feed because Object Replication is enabled. Accounts under an object replication policy can now declare change_feed_enabled = true. The default keeps the current behaviour.
mmeurshanab
approved these changes
Aug 12, 2026
kfaessen
added a commit
that referenced
this pull request
Aug 12, 2026
…#9281) (#462) Follow-up to #461. Object replication requires both the change feed and blob versioning on the source account, and Azure rejects an update that turns either off. With change_feed_enabled configurable the next apply moved on to InvalidRequestPropertyValue: The value 'False' is not allowed for property isVersioningEnabled because Object Replication is enabled. Accounts under an object replication policy can now declare versioning_enabled = true. The default keeps the current behaviour. Co-authored-by: Kelly Faessen <kelly@faessen.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Azure houdt de change feed aan zolang een object-replication policy het account als bron gebruikt, en weigert elke update die hem uitzet. De module zette
change_feed_enabledniet, dus de provider stuurde zijn defaultfalsemee en elke apply op zo'n account faalde met:Bij VWT/Hanab blokkeert dit sinds kort alle deploys naar dev en tst: op
sthtiip4pstst,sthtiintplatformtst,sthtiipserviceticketststensthtiticketslogicapptststaan object-replication policies naar accounts inWest-Europe-we-pod01-prot1. Het storage_account-unit faalt en alles wat ervan afhangt wordt overgeslagen. Acc en prd hebben die policies niet en zijn niet geraakt.Accounts onder zo'n policy kunnen nu
change_feed_enabled = truemeegeven. De default blijftfalse, dus voor alle bestaande callers verandert er niets.storage_account_privateheeft geenblob_properties-blok en is dus niet geraakt.Getest met
terraform fmt -checkenterraform validatetegen azurerm ~> 3.117.