Skip to content

ICL TCO policy ordering conflictsΒ #6589

@MatthewLemmond

Description

@MatthewLemmond

There are issues when running ibm_logs_policy to update previously created policies to remove and replace, there are ordering issues in the subsequently created policies causing failures

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

Terraform CLI and Terraform IBM Provider Version

version: 1.85.0

Affected Resource(s)

  • ibm_logs_policy

Terraform Configuration Files

Please include all Terraform configurations required to reproduce the bug. Bug reports without a functional reproduction may be closed without investigation.

# Copy-paste your Terraform configurations here - for large Terraform configs,
# please share a link to the ZIP file.

Debug Output

Panic Output

Expected Behavior

Create new logs policy in addition to the old policies from previous runs

Actual Behavior

logs policy ordering error when deleting and adding a new policy

Steps to Reproduce

  1. terraform apply

Important Factoids

This occurs on runs after the initial, if a logs policy is removed and another is added at the same time then there will be a duplicate order number error

References

  • #0000

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions