GitHub puppet-grafana
12
12
34
Puppet module to manage Grafana

Metadata Valid
No translation
Correct Puppet Version Range
Supported Puppet version range is %{PUPPET_VERSION_RANGE}
With Puppet Version Range
Puppet version range is present in requirements in metadata.json
With Operatingsystem Support
No translation
Supports Only Current Debian
No translation
Supports Latest Debian
No translation
Supports Only Current Ubuntu
No translation
Supports Latest Ubuntu
No translation
Supports Only Current Centos
No translation
Supports Latest Centos
No translation
Supports Only Current Freebsd
No translation
Supports Latest Freebsd
No translation
In Modulesync Repo
No translation
In Plumbing
Is in plumbing
Has Secrets
Has a .sync.yml file
Synced
Has a .msync.yml file
Latest Modulesync
No translation
Has Modulesync
Is present in voxpupuli/modulesync_config/managed_modules.yml
Released
Is in modulesync_config and in forge releases.
Reference Dot Md
The repository has a REFERENCE.md. It needs to be generated / puppet-strings documentation is missing.

Open Pull Requests

Don't manage dashboard path when puppetsource is not set
bug
needs-tests

Pull Request (PR) description

I manage the dashboard provider path with vcsrepo.
This path is however also managed in config.pp and will purge every file after it is cloned.

The path should not be managed from config.pp if puppetsource is not set in my opinion.

This Pull Request (PR) fixes the following issues

186

Simplify folder finding logic
enhancement
tests-fail
Mask/redact password and secure_json_data in grafana_datasource
bug
merge-conflicts

Previously, when configuring a datasource with a password, the grafana_datasource resource would leak on the CLI and in the puppet report:

```shell
Notice: /Stage[main]/Profile::Grafana/Grafanadatasource[postgres]/securejsondata: securejson_data changed to {
'password' => 'mysweetpassword1'
} (corrective)

```

Now with this fix, the password or secure_json_data field changes emit the following diff:

shell
Notice: /Stage[main]/Profile::Grafana/Grafana_datasource[postgres]/secure_json_data: changed [redacted] to [redacted]

There were also several linting / whitespace issues caught by CI, i've fixed these in the PR.

include the httpMode option in json data
tests-fail

Pull Request (PR) description

include the httpMode option in json data

This Pull Request (PR) fixes the following issues

n/a

Support installing grafana plugins from urls
tests-fail

<!--
Thank you for contributing to this project!

-->

Pull Request (PR) description

This PR enables installing plugins via the "--pluginUrl" flag available in the grafana cli by adding an optional parameter to the grafana_plugin defined type. This was implemented based on the existing "repo" parameter that is already supported.

This Pull Request (PR) fixes the following issues

Fixes #173

Add acceptance test with archive install_method
needs-feedback
tests-fail

This will replace #141.

Add acceptance test with archive install_method
merge-conflicts
needs-rebase
tests-fail

Pull Request (PR) description

This PR aims to add acceptance tests for install_method set to archive

Add possibilities to use custom system grafana user and group.
enhancement
merge-conflicts
needs-rebase
needs-tests

Added possibilities to use custom system grafana user and group for archive installation method.

<!--
Thank you for contributing to this project!

-->

Pull Request (PR) description

<!--
Replace this comment with a description of your pull request.
-->

This Pull Request (PR) fixes the following issues

<!--
Replace this comment with the list of issues or n/a.
Use format:
Fixes #123
Fixes #124
-->

Allow multiple puppetsource

Pull Request (PR) description

Add possibility to use multiple puppetsource for provisioned dashboard by default.

This Pull Request (PR) fixes the following issues

Fixes #130

Ensure all API types have grafana_conn_validator autorequires

<!--
Thank you for contributing to this project!

-->

Pull Request (PR) description

<!--
Replace this comment with a description of your pull request.
-->
Some newer API types did not get added with autorequires on Grafanaconnvalidator so this gets those new types to have same autorequirement as other types to ensure the API is ready before executing API commands.

Add unit tests around grafanaconnvalidator autorequires

Don't manage dashboard path when puppetsource is not set

<!--
Thank you for contributing to this project!

-->

Pull Request (PR) description

<!--
Replace this comment with a description of your pull request.
-->
Handle case where puppetsource is not defined. The way I use this is I deploy my dashboards with a massive git repo and define lots of provisioning dashboards based on sub directories in that git repo by omitting puppetsource.

This is a continuation on #187