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

Issue with multiple groups within the same namespace #22

Open
oludayofafiolu opened this issue Nov 24, 2023 · 0 comments
Open

Issue with multiple groups within the same namespace #22

oludayofafiolu opened this issue Nov 24, 2023 · 0 comments

Comments

@oludayofafiolu
Copy link

oludayofafiolu commented Nov 24, 2023

Hi there,

Thank you for opening an issue. Please note that we try to keep the Terraform issue tracker reserved for bug reports and feature requests. For general usage questions, please see: https://www.terraform.io/community.html.

Terraform Version

Terraform v1.4.0

Affected Resource(s)

  • mimirtool_ruler_namespace

If this issue appears to affect multiple resources, it may be an issue with Terraform's core, so please mention this.

Terraform Configuration Files

locals {
    test1_yaml = yamldecode(file("test-1.yaml"))
    test2_yaml = yamldecode(file("test-2.yaml"))
    test3_yaml = yamldecode(file("test-3.yaml"))
    test4_yaml = yamldecode(file("test-4.yaml"))
}

resource "mimirtool_ruler_namespace" "Test1" {
  namespace                   = "Test"
  config_yaml                 = yamlencode(local.test1_yaml)
  strict_recording_rule_check = true
}


resource "mimirtool_ruler_namespace" "Test2" {
  namespace                   = "Test"
  config_yaml                 = yamlencode(local.test2_yaml)
  strict_recording_rule_check = true
}

resource "mimirtool_ruler_namespace" "Test3" {
  namespace                   = "Test"
  config_yaml                 = yamlencode(local.test2_yaml)
  strict_recording_rule_check = true
}

resource "mimirtool_ruler_namespace" "Test4" {
  namespace                   = "Test"
  config_yaml                 = yamlencode(local.test2_yaml)
  strict_recording_rule_check = true
}

Steps to Reproduce

Please list the steps required to reproduce the issue, for example:

  1. have alerts in the same namespace but in different group
  2. apply the alerts
  3. edit one alert ( this is where the issue is said starts to to happen the other alerts you didn't edit get overwritten )
  4. terraform plan/apply, you will see that it not only edits the changed alert but all alerts in that namespace
  5. then try and delete and you get these errors

Important Factoids

I have had a look at the go and all request are done on a per namespace, it should be done on per namespace and per group

domtes-form3 pushed a commit to domtes-form3/terraform-provider-mimirtool that referenced this issue Feb 29, 2024
…g/x/net-0.17.0

Bump golang.org/x/net from 0.11.0 to 0.17.0
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant