-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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
Neptune create from snapshot results in "InvalidParameterValue: The parameter ResourceName must be provided and must not be blank." #11752
Comments
Still no solution for this? |
still it is continuing, is there any timeline to give a solution for this ? We are trying to create a new cluster with encryption by an existing Neptune cluster snapshot, but could not do for this reason my info
|
I've hit the same issue today, it seems it's still not fixed :( |
I could fix it locally by doing the Existing Code I was able to build terraform-provider-aws with the fix and validate it by creating the neptune cluster from a snapshot. However, I am not able to run the tests. Also, am not able to create a pull request. git push fails with the following error:
Can someone take this change and process it? |
The issue still persists and its a blocker for planning disaster recovery automation via terraform for neptune DB. Can someone please fix this. |
@chungath Sounds like you have a fix for this. Did you apply a fix to a I think you should be able to push to a fork and then create a PR from it on this repo. |
Is there any workaround for this issue? |
The workaround is to not create any tags on the neptune cluster. |
@chungath Thanks, that seems to have fixed the issue for now |
Hey y'all 👋 Thank you for taking the time to file this issue, and for the ongoing discussion. Given that there's been a number of AWS provider releases since the last update on this issue, can anyone confirm whether you're still experiencing this behavior? |
I just ran into it as well. Tried to create from snapshot and wouldn't let me due to tags. Removed them and it worked. |
#25972 attempts to fix this. It's basically tries to include the change proposed by @chungath, though the referenced file has moved/changed. @chungath: Maybe you could have a quick look whether it captures your intent. I'm neither familiar with Terraform nor Go but rather trying to get an internal showstopper resolved. |
…ashicorp#11752 (comment)), tags may not be set when the resource is new, since there's no value for arn yet" This reverts commit 482a86e.
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. |
I'm seeing a similar issue to #5360, but when provisioning a Neptune cluster with tagging from an existing snapshot.
Community Note
Terraform Version
Affected Resource(s)
Terraform Configuration Files
Debug Output
Expected Behavior
Neptune Cluster created from snapshot
Actual Behavior
Above error is thrown, base cluster is created, but apply fails and instances are not created.
Steps to Reproduce
terraform apply
References
The text was updated successfully, but these errors were encountered: