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

Spanner database with DDL recreated after import #3335

Closed
rolandkool opened this issue Mar 28, 2019 · 3 comments
Closed

Spanner database with DDL recreated after import #3335

rolandkool opened this issue Mar 28, 2019 · 3 comments

Comments

@rolandkool
Copy link
Contributor

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 "me too" comments, 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
  • If an issue is assigned to the "modular-magician" user, it is either in the process of being autogenerated, or is planned to be autogenerated soon. If an issue is assigned to a user, that user is claiming responsibility for the issue. If an issue is assigned to "hashibot", a community member has claimed the issue already.

Terraform Version

Provider 2.1

Affected Resource(s)

  • google_spanner_database

Expected Behavior

Terraform should recreate the state before it got lost, including the DDL information.

Actual Behavior

After an import, terraform detects a change in DDL and recreates your database.

Steps to Reproduce

  1. Take the example spanner database from https://www.terraform.io/docs/providers/google/r/spanner_database.html
  2. Create the instance and database by doing an apply
  3. Delete the terraform state file
  4. Run an import
  5. Run apply again

References

@ghost ghost added the bug label Mar 28, 2019
@Chupaka
Copy link
Contributor

Chupaka commented Apr 1, 2019

Looks like your attachment with the log is lost.

@rileykarson
Copy link
Collaborator

This is expected behaviour unfortunately; Terraform has no way of recovering what the ddl/extraStatements provided at creation time were, so you'll see a diff. This is an unintuitive interaction, and isn't a great behaviour- but these kind of creation-only fields aren't able to be represented well by the Terraform provider SDK.

@ghost
Copy link

ghost commented May 3, 2019

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 feel this issue should be reopened, we encourage creating a new issue linking back to this one for added context. If you feel I made an error 🤖 🙉 , please reach out to my human friends 👉 [email protected]. Thanks!

@ghost ghost locked and limited conversation to collaborators May 3, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants