-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
[Metricbeat] gcp: fix integration tests #28364
Conversation
Pinging @elastic/integrations (Team:Integrations) |
💚 Build Succeeded
Expand to view the summary
Build stats
Test stats 🧪
💚 Flaky test reportTests succeeded. 🤖 GitHub commentsTo re-run your PR in the CI, just comment with:
|
This pull request is now in conflicts. Could you fix it? 🙏
|
GCP SDK require GCP_* based variable for a correct initialization. In our tests for GCP module we require GCP_PROJECT_ID and GCP_CREDENTIALS_FILE_PATH to be set.
GCP Billing tests require access to the billing account. This access is restricted and will not be granted to everyone working on beats. In order to be able to run integration tests without a always-failing gcp.billing tests, adding this tag allow to skip billing tests unless specified.
(cherry picked from commit e8066e9) # Conflicts: # x-pack/metricbeat/module/gcp/DEVELOPMENT.md # x-pack/metricbeat/module/gcp/billing/billing_integration_test.go
(cherry picked from commit e8066e9)
(cherry picked from commit e8066e9)
Co-authored-by: endorama <[email protected]>
What does this PR do?
Provide fixes for
gcp
metricbeat module integration tests.Why is it important?
Checklist
I have commented my code, particularly in hard-to-understand areasI have made corresponding change to the default configuration filesCHANGELOG.next.asciidoc
orCHANGELOG-developer.next.asciidoc
.Author's Checklist
How to test this PR locally
TEST_TAGS=gcp MODULE=gcp mage goIntegTest
Related issues
Use cases
Screenshots
Logs