8000 feat(azure): move Watcher pricing from azurerm_automation_account to azurerm_automation_watcher by ptdatta · Pull Request #3417 · infracost/infracost · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

feat(azure): move Watcher pricing from azurerm_automation_account to azurerm_automation_watcher #3417

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

feat(azure): move Watcher pricing from azurerm_automation_account to azurerm_automation_watcher #3417

wants to merge 1 commit into from

Conversation

ptdatta
Copy link
@ptdatta ptdatta commented Jul 1, 2025

Summary

This PR migrates the Watcher cost component from azurerm_automation_account to the standalone azurerm_automation_watcher resource to better align with Azure's pricing model.

Changes

  • Removed the monthly_watcher_hrs usage field and Watchers cost logic from azurerm_automation_account.
  • Added a new azurerm_automation_watcher resource implementation that includes a flat hourly cost component.
  • Registered the new watcher resource in the Terraform provider.
  • Added a new test fixture and .golden file for azurerm_automation_watcher.
  • Updated the usage and golden files for azurerm_automation_account to reflect the removal of Watchers.
  • Cleaned up unused usage schema and methods (e.g., watchersCostComponent, PopulateUsage).

Reasoning

Azure bills Watchers as individual, continuously running resources — not as a usage-based feature of automation accounts. Moving this cost component to its own resource improves accuracy and clarity for users.

Impact

  • Users will now see Watcher costs listed under azurerm_automation_watcher, not azurerm_automation_account.
  • Usage-based estimation for Watchers is no longer required or supported.
  • Golden test output and usage files have been updated to reflect the correct behavior.

Closes: #2430

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.

Add support for azurerm_automation_watcher
1 participant
@ptdatta
0