Fix a typo and a bug in gcp integration package#3821
Merged
Conversation
60s is the minimum valid period, any number less that it creates an error when the Agent tries to run this configuration.
gcp integration package
🌐 Coverage report
|
efd6
approved these changes
Jul 25, 2022
tommyers-elastic
approved these changes
Jul 25, 2022
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What does this PR do?
While testing the
gcpintegration I noticed there have been a regression in the GCP Billing policy templated (incorrectly namedBilline), and found a bug in the GCP Compute defaultperiodvalue (which was10swhen the minimum acceptable in Metricbeat is60s; this produces an error if trying to run the default configuration).Checklist
changelog.ymlfile.Author's Checklist
How to test this PR locally
Related issues
Screenshots