Skip to content

Commit

Permalink
Update stakater/.github action to v0.0.117 (#172)
Browse files Browse the repository at this point in the history
* Update stakater/.github action to v0.0.117

* update

---------

Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Karl Johan Grahn <[email protected]>
  • Loading branch information
renovate[bot] and karl-johan-grahn authored Feb 5, 2025
1 parent ed97b43 commit 833b0d8
Show file tree
Hide file tree
Showing 2 changed files with 3 additions and 3 deletions.
2 changes: 1 addition & 1 deletion .github/workflows/pull_request.yml
Original file line number Diff line number Diff line change
Expand Up @@ -7,7 +7,7 @@ on:

jobs:
qa:
uses: stakater/.github/.github/workflows/[email protected].114
uses: stakater/.github/.github/workflows/[email protected].117
with:
MD_CONFIG: .github/md_config.json
DOC_SRC: README.md
Expand Down
4 changes: 2 additions & 2 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ Grafana Cloud is a fully managed observability platform from Grafana Labs, provi

### Problem

Manually configuring Grafana OnCall on a cluster involves several complex steps, including creating accounts, configuring integrations, and editing configurations. This process is time-consuming, error-prone, and can lead to inconsistencies and misconfigurations if not done accurately. Automating these tasks with the Grafana Cloud Operator simplifies the setup, reduces errors, and ensures consistency across clusters.
Manually configuring Grafana OnCall on a cluster involves several complex steps, including creating accounts, configuring integrations, and editing configurations. This process is time-consuming, error-prone, and can lead to inconsistencies and mis-configurations if not done accurately. Automating these tasks with the Grafana Cloud Operator simplifies the setup, reduces errors, and ensures consistency across clusters.

### SLO Dashboard Management

Expand Down Expand Up @@ -359,7 +359,7 @@ Here's a step-by-step guide on understanding and applying this configuration:
- `sloObservabilityVersion`: You can use this field to use any available release for the SLO Dashboards
- `sloDashboardAPIToken`: Since the operator needs to interact with Grafana Dashboards API, you need to provide it with an API token. This token is stored within a Kubernetes secret for security, and here you point the operator to the right secret and key.
- `grafanaAPIToken`: Since the operator needs to interact with Grafana OnCall's API, you need to provide it with an API token. This token is stored within a Kubernetes secret for security, and here you point the operator to the right secret and key.
- `provisionMode`: Indicates how the operator should function. It could be in a 'hubAndSpoke' mode where it manages multiple clusters or 'standaloneCluster' for managing a single cluster.
- `provisionMode`: Indicates how the operator should function. It could be in a 'hubAndSpoke' mode where it manages multiple clusters or `standaloneCluster` for managing a single cluster.
- `slackId`: For `standalone` provision mode populate this field to connect Slack Channel to Grafana OnCall Integration.
- `slack`: This is toggle for slack alerts to channel. It accepts boolean. By default, it set to true.
Expand Down

0 comments on commit 833b0d8

Please sign in to comment.