Back
BUG: Updating new API key removes scopes
If you create a new API key from the cloud console and, for example, add all the "Database" scopes, it says that the key has 16 scopes after creating it.
If you then update the name of the key (or anything I imagine), it goes down to 10 scopes.
I imagine it has to do with the new update, because the scopes that are removed are "row.read, row.update, etc."
TL;DR
Developers are experiencing a bug where updating a new API key removes scopes. Creating a new API key with scopes results in 16 scopes, but updating the key lowers it to 10 scopes. It seems to be related to a recent update, as specific scopes like "row.read" and "row.update" are being removed.BUG: Updating new API key removes scopes
