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

"aws_cloudwatch_log_subscription_filter" 's argument "role_arn" doesn't produce changes if set to null #35506

Open
francescosolari0 opened this issue Jan 26, 2024 · 1 comment
Labels
bug Addresses a defect in current functionality. service/logs Issues and PRs that pertain to the logs service.

Comments

@francescosolari0
Copy link

francescosolari0 commented Jan 26, 2024

Terraform Core Version

1.6.2

AWS Provider Version

5.34.0

Affected Resource(s)

After changing the argument role_arn to null for the previously-created resource aws_cloudwatch_log_subscription_filter i got a "no changes" message in my plan

Expected Behavior

When changing the role_arn value from "anything" to "" or null i would expect my next plan to show some changes, more precisely i would expect the following error: "role_arn" (anything) is an invalid ARN: arn: invalid prefix

Actual Behavior

The plan run after changing the argument's value shows no changes

Relevant Error/Panic Output Snippet

No response

Terraform Configuration Files

locals {
  choice = true
}

resource "aws_cloudwatch_log_subscription_filter" "this" {

  count           = local.choice ? 1 : 0

  name            = "name"
  role_arn        = null
  log_group_name  = "log group name"
  filter_pattern  = ""
  destination_arn = "a valid arn"
  distribution    = "ByLogStream"
}

Steps to Reproduce

  1. Create an aws_cloudwatch_log_subscription_filter
  2. Set the value of the argument role_arn to a valid arn
  3. Run an apply and create the resource on AWS
  4. Change the value of the argument role_arn to "" or null

Debug Output

No response

Panic Output

No response

Important Factoids

No response

References

No response

Would you like to implement a fix?

None

@francescosolari0 francescosolari0 added the bug Addresses a defect in current functionality. label Jan 26, 2024
Copy link

Community Note

Voting for Prioritization

  • Please vote on this issue by adding a 👍 reaction to the original post to help the community and maintainers prioritize this request.
  • Please see our prioritization guide for information on how we prioritize.
  • 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.

Volunteering to Work on This Issue

  • If you are interested in working on this issue, please leave a comment.
  • If this would be your first contribution, please review the contribution guide.

@github-actions github-actions bot added the service/logs Issues and PRs that pertain to the logs service. label Jan 26, 2024
@terraform-aws-provider terraform-aws-provider bot added the needs-triage Waiting for first response or review from a maintainer. label Jan 26, 2024
@justinretzolk justinretzolk removed the needs-triage Waiting for first response or review from a maintainer. label Jan 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Addresses a defect in current functionality. service/logs Issues and PRs that pertain to the logs service.
Projects
None yet
Development

No branches or pull requests

2 participants