fix: [DTOSS-13213] Function App retention period days repeatedly reported in Terraform Plan#315
Merged
MacMur85 merged 1 commit intoJun 23, 2026
Conversation
f73e3bf to
303b149
Compare
rfk-nc
approved these changes
Jun 23, 2026
|
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.



Description
After some research, this currently does not have a fix. The value for
retention_period_daysin the state file is being set to zero after any change to the Function App resource (it does not change in the Azure itself). The only way to get rid of this in the plan is to add it to thelifecycle.ignoreblock.Context
Currently it makes the already long Terraform Plan unreadable even if there are no real changes reported.
It will be reverted once there is a fix for the bug in the AzureRM provider.
Type of changes
Checklist
Sensitive Information Declaration
To ensure the utmost confidentiality and protect your and others privacy, we kindly ask you to NOT including PII (Personal Identifiable Information) / PID (Personal Identifiable Data) or any other sensitive data in this PR (Pull Request) and the codebase changes. We will remove any PR that do contain any sensitive information. We really appreciate your cooperation in this matter.