Skip to content

Update local setup for auth in README #31

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
nikimanoledaki merged 1 commit into from
Feb 12, 2025
Merged

Update local setup for auth in README #31

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 5 additions & 2 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,10 +26,13 @@ While these are what we use internally and require, in theory the bot should wor
## Prerequisites for local development

- HTTP access to a prometheus server that has [cloudcost-exporter](https://github.com/grafana/cloudcost-exporter) metrics available
- For example, navigate to `https://<grafana-address>/connections/datasources/`, identify the Prometheus (or Mimir!) datasource to use, and copy the value of `Prometheus server URL`.
- A local copy of the repository that stores kube-manifest files
- See [flux](https://fluxcd.io/flux/guides/repository-structure/) docs a similar structure to what Grafana Labs uses
- If you have a Mimir instance running on Grafana Cloud, create an [access policy token](https://grafana.com/docs/grafana-cloud/account-management/authentication-and-permissions/access-policies/) with `metrics:read` permissions
- Create a yaml file with basic auth creds to use. Replace password with the token you created earlier.
- If you have a Mimir instance running on Grafana Cloud, create an [access policy with a token](https://grafana.com/docs/grafana-cloud/account-management/authentication-and-permissions/access-policies/) with `metrics:read` permissions
- Create a yaml file with basic auth creds to use (see below).
- Replace `<user>` with the the username of the datasource account. For example, after finding the datasource to use in `https://<grafana-address>/connections/datasources/`, find the username under `Authentication` > `Basic authentiaction` > `User`.
- Replace `<password>` with the token you created earlier.

```yaml
basic_auth:
Expand Down