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

[Bug] Passing replica count in pod spec errors #8

Closed
haruska opened this issue Apr 8, 2024 · 0 comments · Fixed by #15
Closed

[Bug] Passing replica count in pod spec errors #8

haruska opened this issue Apr 8, 2024 · 0 comments · Fixed by #15
Labels
bug Something isn't working

Comments

@haruska
Copy link
Collaborator

haruska commented Apr 8, 2024

Current Behavior

Attempting to create a pod index with a replica count of 2 produces an error.

resource "pinecone_index" "test-rep" {
  name = "tf-test-rep"
  dimension = 2
  spec = {
    pod = {
      environment = "us-west4-gcp"
      pod_type    = "s1.x1"
      replicas = 2
    }
  }
}

Output

│ Error: Provider produced inconsistent result after apply
│
│ When applying changes to pinecone_index.jenpod3, provider "provider[\"registry.terraform.io/pinecone-io/pinecone\"]" produced an unexpected new value:
│ .spec.pod.pods: was cty.NumberIntVal(1), but now cty.NumberIntVal(2).
│
│ This is a bug in the provider, which should be reported in the provider's own issue tracker.

Expected Behavior

Would expect the index to be created with the correct number of replicas.

Steps To Reproduce

  1. Attempt to create an index with a replica count (ex above)

Additional Context

reported by @jhamon

@haruska haruska added the bug Something isn't working label Apr 8, 2024
skyscrapr added a commit to skyscrapr/terraform-provider-pinecone that referenced this issue Apr 9, 2024
haruska pushed a commit that referenced this issue Apr 10, 2024
@haruska haruska linked a pull request Apr 10, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant