Bicep resource updates blocked by default maxMajorIncrement #44324
Unanswered
GodVenn
asked this question in
Request Help
Replies: 1 comment
-
|
I agree with this being an issue, but I don;t like the threshold idea. Instead I'd prefer to ignore apply maxMajorIncrement to versions which are not semver-like or do not have a meaningful major, minor separation. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
How are you running Renovate?
Self-hosted Renovate CLI
Which platform you running Renovate on?
GitHub.com
Which version of Renovate are you using?
43.220.0
Please tell us more about your question or problem
Hi!
I want to start off by saying that I really appreciate your product and the work you have put into making it so configurable and flexible - great work!
I am using the
azure-bicep-resourcedatasource, but noticed that I never got any updates, nor any pending PRs.Checking the debug logs revealed that the updates were silently getting dropped because bicep resources uses date-versioning, so it was hitting the
maxMajorIncrementwhen attempting to update from one year to another.Example:
Current version
resource keyvault 'Microsoft.KeyVault/vaults@2024-11-01'Log message:
DEBUG: Skipping Microsoft.KeyVault/vaults@2025-05-01 because major increment 9400 exceeds maxMajorIncrement 500I can fix this by changing the
maxMajorIncrement, but IMO, the default for the bicep resource datasource should be set to a reasonable limit, disabled OR at least added as pending to visualize this to the users.I think the suggestion in #42820 would be a good mitigation as well, as it could implicitly disable it for bicep modules by setting the
maxMajorIncrementThresholdto 900 or something like that.Logs (if relevant)
Logs
Beta Was this translation helpful? Give feedback.
All reactions