You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is this your first time submitting a feature request?
I have searched the existing issues, and I could not find an existing issue for this feature
I am requesting a straightforward extension of existing functionality
Describe the feature
Currently, the property pinecone.PineconeIndex.name is required. Instead, the Pinecone provider should use autonaming.
With autonaming, a Pulumi resource like the following:
constpineconeIndex=newpinecone.PineconeIndex("pinecone-index",{// name property intentionally omitted as it would no longer be requiredmetric: pinecone.IndexMetric.Cosine,dimension: 384,spec: {serverless: {cloud: pinecone.ServerlessSpecCloud.Aws,region: AWS_REGION,},},},{provider: pineconeProvider});
Would produce a physical name like pinecone-index-abc123 where abc123 is a random hex suffix. The suffix allows users to deploy multiple stacks in the same Pinecone index. The resolved value of name would still be accessible in other resources. name can also be explicitly specified if needed.
Describe alternatives you've considered
No response
Who will this benefit?
No response
Are you interested in contributing this feature?
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered:
Is this your first time submitting a feature request?
Describe the feature
Currently, the property
pinecone.PineconeIndex.name
is required. Instead, the Pinecone provider should use autonaming.With autonaming, a Pulumi resource like the following:
Would produce a physical name like
pinecone-index-abc123
whereabc123
is a random hex suffix. The suffix allows users to deploy multiple stacks in the same Pinecone index. The resolved value ofname
would still be accessible in other resources.name
can also be explicitly specified if needed.Describe alternatives you've considered
No response
Who will this benefit?
No response
Are you interested in contributing this feature?
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: