Skip to content
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.

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

azurerm_maintenance_configuration should support declaration of dynamic scopes #24411

Closed
1 task done
qaaditya opened this issue Jan 5, 2024 · 6 comments · Fixed by #25467
Closed
1 task done

azurerm_maintenance_configuration should support declaration of dynamic scopes #24411

qaaditya opened this issue Jan 5, 2024 · 6 comments · Fixed by #25467

Comments

@qaaditya
Copy link

qaaditya commented Jan 5, 2024

Is there an existing issue for this?

  • I have searched the existing issues

Community Note

  • Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
  • Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
  • If you are interested in working on this issue or have submitted a pull request, please leave a comment and review the contribution guide to help.

Description

The current version does not support declaration of "Dynamic scopes" using filters and tags

New or Affected Resource(s)/Data Source(s)

azurerm_maintenance_configuration

Potential Terraform Configuration

resource "azurerm_resource_group" "int_ussc_patching" {
  name     = "int-ussc-patching"
  location = "South Central US"
}

resource "azurerm_maintenance_configuration" "int_ussc_patching" {
  name                = "int-ussc-patching"
  resource_group_name = azurerm_resource_group.int_ussc_patching.name
  location            = azurerm_resource_group.int_ussc_patching.location
  scope               = "InGuestPatch"

  window {
    start_date_time = "2024-01-05 21:00"
    duration        = "03:55"
    time_zone       = "Central Standard Time"
    recur_every     = "1Week Tuesday"
  }

  install_patches {
    windows {
      classifications_to_include = ["Critical", "Security", "UpdateRollup", "Definition", "Updates"]
    }
  }

  dynamic_scopes {

    <dynamic_scope_1> {
      subscription = "int-ae-01"
      filter_by_tags = {
        os_types                = "windows"
        role                    = "App Hosts"
        update_management_group = "1"
      }
    }

    <dynamic_scope_2> {
      subscription = "int-ae-01"
      filter_by_tags = {
        os_types                = "linux"
        role                    = "App Hosts"
        update_management_group = "2"
      }
    }
  }
}

References

No response

@PLagrandmaison
Copy link

Hello, any updates on this topic or visibility on this possible feature?

@AKowsigan
Copy link

Hello, any updates on this topic or visibility on this possible feature?

Did you find any solution to do it in Terraform please ?

@ASHR4
Copy link
Contributor

ASHR4 commented Feb 27, 2024

Hello, any updates on this topic or visibility on this possible feature?

Did you find any solution to do it in Terraform please ?

I'm currently working on this.

Can't guarantee when it'll be available as it requires a review

@leewilson86
Copy link
Contributor

Is someone able to pick up on the latest comments on the attached PR? #25467

I have a need for this feature too, so it would be great if the author and reviewers can assist in getting this merged in fairly soon.

Thanks

@hristodragolovbede
Copy link

I think this can be quite handy for me too. I'd prefer having a more dynamic way of managing and assigning maintenance windows to VMs than doing a static assignment.

@github-actions github-actions bot added this to the v3.103.0 milestone May 6, 2024
Copy link

github-actions bot commented Jun 6, 2024

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators Jun 6, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

7 participants