-
Notifications
You must be signed in to change notification settings - Fork 18
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
Add Support for AlloyDB #918
Comments
Hello @geekflyer, this native provider is generated from Google specs returned from the Discovery API:
I pulled the latest contents from this endpoint, but the result doesn't contain any reference to |
Thanks for the investigation @ringods I'm going to close this as it appears the specifications haven't been made available for discovery yet. As soon as they are, this should be automatically included and shouldn't require any action on our part. |
Discovery documents are available in https://alloydb.googleapis.com/$discovery/rest?version=v1 @danielrbradley I don't think we should close the issue until we ship the feature. We should mark it as awaiting-upstream if it's blocked. |
I reached out to our GCP account team to see why this is not in the central discovery API yet and get its inclusion prioritized fyi. |
This is now fixed by GCP - the discovery doc is now available at https://discovery.googleapis.com/discovery/v1/apis?name=alloydb. The next release of this provider should pick up these APIs. |
Hi,
currently seems like AlloyDB isn't supported (which is a new API namespace).
It's already supported in the classic provider: https://www.pulumi.com/registry/packages/gcp/api-docs/alloydb/cluster/
Can we please add to the native provider?
The classic / tf provider doesn't expose certain backup options like continuous backup, so I'd like to use the native one instead.
Best, Christian
The text was updated successfully, but these errors were encountered: