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

[Feature] Autonaming #99

Open
2 tasks done
jkodroff opened this issue Jun 20, 2024 · 0 comments
Open
2 tasks done

[Feature] Autonaming #99

jkodroff opened this issue Jun 20, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@jkodroff
Copy link

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:

const pineconeIndex = new pinecone.PineconeIndex("pinecone-index", {
        // name property intentionally omitted as it would no longer be required
	metric: 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

@jkodroff jkodroff added the enhancement New feature or request label Jun 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant