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

Invalid Attribute Value Match with pingone_alert_channel #941

Closed
corvettii opened this issue Nov 20, 2024 · 1 comment · Fixed by #953
Closed

Invalid Attribute Value Match with pingone_alert_channel #941

corvettii opened this issue Nov 20, 2024 · 1 comment · Fixed by #953
Assignees
Labels
status/triaged The issue/PR has completed initial triage and needs assignment type/bug Something isn't working
Milestone

Comments

@corvettii
Copy link

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 other comments that do not add relevant new information or questions, 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

PingOne Terraform provider Version

v1.1.1

Terraform Version

v1.9.8

Affected Resource(s)

  • pingone_alert_channel

Terraform Configuration Files

resource "pingone_alert_channel" "all_alerts" {
  environment_id = 12345678-1234-1234-1234-12345678beef
  alert_name = "All"
  channel_type = "EMAIL"

  addresses = [
    alerts@example.com",
  ]

  include_alert_types = [
    "CERTIFICATE_EXPIRED",
    "CERTIFICATE_EXPIRING",
    "GATEWAY_VERSION_DEPRECATED",
    "GATEWAY_VERSION_DEPRECATING",
    "KEY_PAIR_EXPIRED",
    "KEY_PAIR_EXPIRING",
    "LICENSE_90_PERCENT_USER_SOFT_LIMIT",
    "LICENSE_EXPIRED",
    "LICENSE_EXPIRING",
    "LICENSE_ROTATED",
    "LICENSE_USER_HARD_LIMIT_EXCEEDED",
    "LICENSE_USER_SOFT_LIMIT_EXCEEDED",
    "RISK_CONFIGURATION",
    "SUSPICIOUS_TRAFFIC",
  ]

  include_severities = [
    "ERROR",
    "INFO",
    "WARNING",
  ]
}

Debug Output

╷
│ Error: Invalid Attribute Value Match
│ 
│   with pingone_alert_channel.all_alerts,
│   on alerts.tf line 10, in resource "pingone_alert_channel" "all_alerts":
│   10:   include_alert_types = [
│   11:     "CERTIFICATE_EXPIRED",
│   12:     "CERTIFICATE_EXPIRING",
│   13:     "GATEWAY_VERSION_DEPRECATED",
│   14:     "GATEWAY_VERSION_DEPRECATING",
│   15:     "KEY_PAIR_EXPIRED",
│   16:     "KEY_PAIR_EXPIRING",
│   17:     "LICENSE_90_PERCENT_USER_SOFT_LIMIT",
│   18:     "LICENSE_EXPIRED",
│   19:     "LICENSE_EXPIRING",
│   20:     "LICENSE_ROTATED",
│   21:     "LICENSE_USER_HARD_LIMIT_EXCEEDED",
│   22:     "LICENSE_USER_SOFT_LIMIT_EXCEEDED",
│   23:     "RISK_CONFIGURATION",
│   24:     "SUSPICIOUS_TRAFFIC",
│   25:   ]
│ 
│ Attribute include_alert_types[Value("SUSPICIOUS_TRAFFIC")] value must be one of: ["CERTIFICATE_EXPIRED" "CERTIFICATE_EXPIRING" "KEY_PAIR_EXPIRED" "KEY_PAIR_EXPIRING" "GATEWAY_VERSION_DEPRECATED" "GATEWAY_VERSION_DEPRECATING" "LICENSE_90_PERCENT_USER_SOFT_LIMIT" "LICENSE_EXPIRED" "LICENSE_EXPIRING"
│ "LICENSE_ROTATED" "LICENSE_USER_HARD_LIMIT_EXCEEDED" "LICENSE_USER_SOFT_LIMIT_EXCEEDED" "RISK_CONFIGURATION"], got: "SUSPICIOUS_TRAFFIC"
╵

Panic Output

N/A

Expected Behavior

SUSPICIOUS_TRAFFIC is a valid option.

Actual Behavior

Not allowed.

Steps to Reproduce

  1. terraform apply

Important Factoids

N/A

References

N/A

@corvettii corvettii added status/needs-triage The issue/PR needs initial triage type/bug Something isn't working labels Nov 20, 2024
@patrickcping
Copy link
Collaborator

hi @corvettii thanks for raising! I'll look to get this included in the next minor release

@patrickcping patrickcping added this to the v1.3.0 milestone Nov 25, 2024
@patrickcping patrickcping added status/triaged The issue/PR has completed initial triage and needs assignment and removed status/needs-triage The issue/PR needs initial triage labels Nov 25, 2024
@patrickcping patrickcping self-assigned this Nov 25, 2024
@patrickcping patrickcping added the status/blocked/upstream-sdk The issue/PR is blocked by an upstream SDK label Nov 25, 2024
@patrickcping patrickcping linked a pull request Dec 18, 2024 that will close this issue
@patrickcping patrickcping removed the status/blocked/upstream-sdk The issue/PR is blocked by an upstream SDK label Dec 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status/triaged The issue/PR has completed initial triage and needs assignment type/bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants