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

Firestore database auto-naming incorrect #2183

Closed
VenelinMartinov opened this issue Jul 11, 2024 · 1 comment · Fixed by #2184
Closed

Firestore database auto-naming incorrect #2183

VenelinMartinov opened this issue Jul 11, 2024 · 1 comment · Fixed by #2184
Assignees
Labels
kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed

Comments

@VenelinMartinov
Copy link
Contributor

Describe what happened

Firestore databases need all-lowercase names but we sometimes auto-name them with upper-case letters.

see also #2164

Sample program

name: firestore-field
runtime: yaml
config:
  gcpProj: string
resources:
  myFirestoreDatabase:
    type: gcp:firestore:Database
    properties:
      type: "FIRESTORE_NATIVE"
      project: ${gcpProj}
      locationId: "us-central"

Log output

.

Affected Resource(s)

No response

Output of pulumi about

.

Additional context

No response

Contributing

Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

@VenelinMartinov VenelinMartinov added kind/bug Some behavior is incorrect or out of spec needs-triage Needs attention from the triage team and removed needs-triage Needs attention from the triage team labels Jul 11, 2024
@pulumi-bot pulumi-bot added resolution/fixed This issue was fixed labels Aug 20, 2024
@pulumi-bot
Copy link
Contributor

This issue has been addressed in PR #2184 and shipped in release v7.38.0.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Some behavior is incorrect or out of spec resolution/fixed This issue was fixed
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants