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.

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

Tweak markdown to force operator test workflow #1156

Closed
wants to merge 2 commits into from
Closed

Tweak markdown to force operator test workflow #1156

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
a32e714
Tweak markdown to force operator test workflow
theory Feb 13, 2025
ef3d274
Disable deploying Grafana
nhudson Feb 14, 2025
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
2 changes: 1 addition & 1 deletion tembo-operator/testdata/prometheus-stack.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
alertmanager:
enabled: false
grafana:
enabled: true
enabled: false
env:
datasources:
datasources.yaml:
Expand Down
2 changes: 1 addition & 1 deletion tembo-operator/tests/README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,5 @@
# Integration tests

https://doc.rust-lang.org/book/ch11-03-test-organization.html
[Test Organization](https://doc.rust-lang.org/book/ch11-03-test-organization.html)

> In Rust, integration tests are entirely external to your library. They use your library in the same way any other code would, which means they can only call functions that are part of your library’s public API. Their purpose is to test whether many parts of your library work together correctly. Units of code that work correctly on their own could have problems when integrated, so test coverage of the integrated code is important as well. To create integration tests, you first need a tests directory.
Loading