Skip to content
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.

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

Manually deploy updates to grafana #100

Merged
merged 1 commit into from
Jan 19, 2024
Merged

Manually deploy updates to grafana #100

merged 1 commit into from
Jan 19, 2024

Conversation

lucyb
Copy link
Collaborator

@lucyb lucyb commented Jan 19, 2024

We are not able to determine when an update has been made by dependabot and then automatically deploy that change, due to on: push: not working with the paths option when there's a merge commit.

We are also unable to easily check if grafana has been updated, which means most scheduled runs of the grafana workflow will fail. It means we're unlikely to spot real errors when they happen.

Therefore, we are reverting to manual deployments for now.

We are not able to determine when an update has been made by dependabot and then automatically deploy that change, due to `on: push:` not working with the `paths` option when there's a merge commit.

We are also unable to easily check if grafana has been updated, which means most scheduled runs of the grafana workflow will fail. It means we're unlikely to spot real errors when they happen.

Therefore, we are reverting to manual deployments for now.
@lucyb lucyb force-pushed the manually-deploy-grafana branch from 534b19b to 53ed624 Compare January 19, 2024 16:41
@lucyb lucyb merged commit ef1ba9f into main Jan 19, 2024
7 checks passed
@lucyb lucyb deleted the manually-deploy-grafana branch January 19, 2024 16:48
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants