search

firebase / firebase-tools

The Firebase Command Line Tools
MIT License
4.01k stars 925 forks source link

Updating firestore rules does not add historical log to Firestore Console Rules for a non-default database (multiple databases) #7456

Open memoricab opened 1 month ago

memoricab commented 1 month ago

Hello, We are experiencing an issue which is not reproducible on (default) db but on named db (multiple databases) I'm not sure if this bug should be owned by firebase-cli since Firestore Console is also involved, I reported directly via form as well. If not related here, we can close.

[REQUIRED] Environment info

1.13.3

firebase-tools:

Platform: ubuntu

[REQUIRED] Test case

firebase deploy --only firestore:named-db --project "my-project"

[REQUIRED] Steps to reproduce

Create a named db (multiple databases) Update the rules of named-db as above test case. Go to Firebase Cloud Firestore Console, select the named-db and click on Rules tabs.

[REQUIRED] Expected behavior

I should see the historical log of update on the left side. -for (default) database expected behaviour is reproducible

[REQUIRED] Actual behavior

No new historical log after rules are updated with firebase-cli. Nevertheless, the rules are updated.

aalej commented 1 month ago

Hey @memoricab, thanks for reporting this! I was able to reproduce the behavior you mentioned. One thing I noticed is that, when using the Firebase CLI the historical tab does not get updated, but when updating the rules via the Firebase Console the historical tab would get updated. In both cases, the rules get updated.

I’ll raise this to our engineering team so that we can verify if this is a bug with the Firebase CLI.

memoricab commented 1 month ago

Yes @aalej, forgot to mention sorry, that is correct- if you update the rules of non default db from console it does update the history.