Avoid unnecessary budget changes #1015
Open
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.
Hi, we noticed that almost any change in project settings or change on dependent module, like folder in which the project is created, triggers project number refresh via data resource and plan budget update because of that. The budget update is not performed, because at the apply phase the data resource returns identical project number.
As the project number is immutable thing and it's known and already available in
core_project_factorymodule outputs, I suggest passing it to the budget module directly to avoid using the data resource at all.To keep the budget module backward compatible and still usable as standalone module, it will still fetch the project numbers when they are not provided directly.