💄 Remove auth.google api_url

[sinclairpaul]

Proposed Changes

The checks within recent versions of Grafana appear to look at the ini file to see if the api_url under the auth.google section exists, if it does it generates a rather annoying log message.

Removing the entry resolves this, as config is set via Environment Variables and that this is only used for SSO from Google, I would suggest the impact is low.

Related Issues

#427

Summary by CodeRabbit

• New Features

  • Introduced a new configuration option to allow loading unsigned plugins.

• Updates

  • Changed the default admin password for enhanced security.
  • Updated the default role for new users to Admin.
  • Disabled SMTP email settings.
  • Disabled alerting functionality.

These changes enhance security and user management while providing additional configuration options for Grafana.

[coderabbitai]

Walkthrough

The changes in the pull request focus on the configuration file grafana.ini for Grafana. Key modifications include the introduction of the allow_loading_unsigned_plugins option in the [plugins] section, updates to the admin_password and auto_assign_org_role in the [security] and [users] sections respectively, and adjustments to the enabled settings in both the [smtp] and [alerting] sections. Other sections remain largely unchanged, maintaining existing parameters.

Changes

File Path	Change Summary
grafana/rootfs/etc/grafana/grafana.ini	- Added allow_loading_unsigned_plugins in [plugins] section. - Updated admin_password to hassio in [security] section. - Updated auto_assign_org_role to Admin in [users] section. - Set enabled to false in [smtp] and [alerting] sections.

Poem

In the land of Grafana, where dashboards gleam,
New options sprout like flowers in a dream.
With plugins allowed, and passwords anew,
The settings are fresh, like morning dew.
So hop along, users, let’s celebrate,
With each little change, our data’s first-rate! 🐇✨

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[sinclairpaul]

@coderabbitai The Summary is incorrect

[coderabbitai]

@sinclairpaul Thank you for letting me know that the summary is incorrect. I will regenerate the AI-generated summary to reflect the accurate changes in the PR.

✅ Actions performed

Summary regeneration triggered.

[frenck]

Oh! nice, thanks, @sinclairpaul 👍

../Frenck