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

"snapshot_identifier": conflicts with global_cluster_identifier #358

Closed
1 task done
fplotnikov opened this issue Mar 24, 2023 · 4 comments · Fixed by #335
Closed
1 task done

"snapshot_identifier": conflicts with global_cluster_identifier #358

fplotnikov opened this issue Mar 24, 2023 · 4 comments · Fixed by #335

Comments

@fplotnikov
Copy link

Description

During restore from the snapshot error appear:
"snapshot_identifier": conflicts with global_cluster_identifier

All works fine if snapshot restore doesn't require.

  • ✋ I have searched the open/closed issues and my issue is not listed.

⚠️ Note

Tested on different module version.
Also updated AWS provider to the latest available 4.60.0 which has this issue in the description and marked as fixed - it doesn't help.

Versions

  • Module version [Required]: 7.7.0

  • Terraform version:
    v1.3.4

  • Provider version(s):

  • provider registry.terraform.io/hashicorp/aws v4.60.0
  • provider registry.terraform.io/hashicorp/local v2.4.0
  • provider registry.terraform.io/hashicorp/null v3.2.1
  • provider registry.terraform.io/hashicorp/random v3.4.3
  • provider registry.terraform.io/hashicorp/template v2.2.0

Reproduction Code [Required]

Run RDS creation/update with defined variable - snapshot_identifier

Expected behavior

Create RDS from snapshot.

Actual behavior

Got an error on PLAN run:
│ "snapshot_identifier": conflicts with global_cluster_identifier

@bryantbiggs
Copy link
Member

@pimperator
Copy link

I'm also affected by this: provider version 4.60.0.
workaround is to go with 4.59.0

@antonbabenko
Copy link
Member

This issue has been resolved in version 8.0.0 🎉

@github-actions
Copy link

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues. If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 11, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
4 participants