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

Handle the "unreadable" gceZone in AlloyDBInstance #3368

Open
3 tasks done
maqiuyujoyce opened this issue Dec 12, 2024 · 0 comments
Open
3 tasks done

Handle the "unreadable" gceZone in AlloyDBInstance #3368

maqiuyujoyce opened this issue Dec 12, 2024 · 0 comments
Labels
enhancement New feature or request

Comments

@maqiuyujoyce
Copy link
Collaborator

Checklist

  • I did not find a related open enhancement request.
  • I understand that enhancement requests filed in the GitHub repository are by default low priority.
  • If this request is time-sensitive, I have submitted a corresponding issue with GCP support.

Describe the feature or resource

gceZone is never returned when getting an AlloyDBInstance even if it was configured explicitly. So this field is basically unreadable right now. We should handle it properly.

(The TF resource also has the same issue: hashicorp/terraform-provider-google#13378)

Additional information

No response

Importance

No response

@maqiuyujoyce maqiuyujoyce added the enhancement New feature or request label Dec 12, 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