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

Content with same name already exists error when resource name was changed #673

Open
justin-k-genesys opened this issue Jul 12, 2024 · 0 comments

Comments

@justin-k-genesys
Copy link

We had an existing resource defined such as:

resource "sumologic_content" "some_name"{
    parent_id = 12345
    config = jsonencode({
        "name": "name of saved search"
        ...
    })
}

We made a spelling change to "some_name" and were able to successfully make the change in multiple regions. For 1 region, we got the following error:

Error: Failed - {content1:duplicate_element Content:: Content with same name already exists. Name = name of saved search & Existing Parent ID = 12345 }

By the time I checked the sumologic UI for the region, the saved search was completely gone. The change was attempted again the following day and was successful. I believe there to be some sort of race condition.

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