Repository navigation
docs(operator): grant the usage breakdown tables to the DB user - #314
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
#309 added a DELETE+INSERT rewrite of
app_deployment_service_usageandapp_deployment_volume_usage(lnvps_db/src/mysql.rs:4300-4331) without widening the documented operator grant, which was still SELECT everywhere plus UPDATE onapp_deployment. In production the operator getsDELETE command deniedand every deployment's breakdown stays empty; the totals still update, since those are an UPDATE onapp_deployment.Docs only — the grant itself is applied by hand on the database.
From the lnvps channel.