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.
Description
In Grafana, Dashboard-permissions cannot be more restrictive, than the folders they're in.
Thus it's necessary, to be able to configure the folder-permissions.
I added a new type for folders (together with the obligatory controller, client and config) to do exactly that.
notes / known issues:
uid
will be reproducible generated from the title, making it unique as well.Bugfix:
Along the way, I added more log-output and in
main()
I movedprintVersion()
to be executed after the logger has been set/initialized. Its output was missing from the k8s-log otherwise.Type of change
Checklist
I added a few unit-tests, but not enough to claim, that it proves the effectiveness.
Verification steps
GrafanaFolder
to your configuration.deploy/examples/folders/restricted-folder.yaml
)GrafanaDashboard
in the folder by referencing its title incustomFolderName
/dashboards
in the url-bar)