-
Notifications
You must be signed in to change notification settings - Fork 10.2k
Fix flowtrackd naming in schema map #22978
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
Closed
hyperlint-ai
wants to merge
22
commits into
production
from
hyperlint/automation/repository-scan/5a498e6
Closed
Changes from all commits
Commits
Show all changes
22 commits
Select commit
Hold shift + click to select a range
75684d3
Hyperlint Automation Fix
hyperlint-ai[bot] e850809
Hyperlint Automation Fix
hyperlint-ai[bot] 21fb706
Hyperlint Automation Fix
hyperlint-ai[bot] 024ac4c
Hyperlint Automation Fix
hyperlint-ai[bot] 9079e1d
Hyperlint Automation Fix
hyperlint-ai[bot] 553e9a0
Hyperlint Automation Fix
hyperlint-ai[bot] 54862cb
Hyperlint Automation Fix
hyperlint-ai[bot] aebee56
Hyperlint Automation Fix
hyperlint-ai[bot] 0e8a993
Hyperlint Automation Fix
hyperlint-ai[bot] 348b9a9
Hyperlint Automation Fix
hyperlint-ai[bot] 600bb39
Hyperlint Automation Fix
hyperlint-ai[bot] dd8fb94
Hyperlint Automation Fix
hyperlint-ai[bot] 46aa426
Hyperlint Automation Fix
hyperlint-ai[bot] 9dd82dc
Hyperlint Automation Fix
hyperlint-ai[bot] 9edd847
Hyperlint Automation Fix
hyperlint-ai[bot] da7cee2
Hyperlint Automation Fix
hyperlint-ai[bot] d291078
Hyperlint Automation Fix
hyperlint-ai[bot] 6a05fb7
Hyperlint Automation Fix
hyperlint-ai[bot] b6f1d7f
Hyperlint Automation Fix
hyperlint-ai[bot] ba159b3
Hyperlint Automation Fix
hyperlint-ai[bot] c814d16
Hyperlint Automation Fix
hyperlint-ai[bot] 3617dbd
Hyperlint Automation Fix
hyperlint-ai[bot] File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -6,7 +6,7 @@ title: Querying Firewall Events with GraphQL | |
|
|
||
| In this example, we are going to use the GraphQL Analytics API to query for Firewall Events over a specified time period. | ||
|
|
||
| The following API call will request Firewall Events over a one hour period, and output the requested fields. Be sure to replace `<CLOUDFLARE_ZONE_TAG>`, `<EMAIL>`, and `<API_TOKEN>`[^1] with your zone tag and API credentials, and adjust the `datetime_geg` and `datetime_leq` values to your liking. | ||
| The following API call will request Firewall Events over a one hour period, and output the requested fields. Be sure to replace `<Cloudflare_ZONE_TAG>`, `<EMAIL>`, and `<API_TOKEN>`[^1] with your zone tag and API credentials, and adjust the `datetime_geq` and `datetime_leq` values to your liking. | ||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. There's a typo in the parameter name in the text. It says 'datetime_geg' in the original text which was corrected to 'datetime_geq' in this PR, matching the actual parameter used in the code example. |
||
|
|
||
| ## API Call | ||
|
|
||
|
|
@@ -183,4 +183,4 @@ https://api.cloudflare.com/client/v4/graphql \ | |
| #=> } | ||
| ``` | ||
|
|
||
| [^1]: Refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/) for more information on configuration and permissions. | ||
| [^1]: Refer to [Configure an Analytics API token](/analytics/graphql-api/getting-started/authentication/api-token-auth/) for more information on configuration and permissions. | ||
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There's an inconsistency in the formatting between the two instances of 'flowtrackedNetworkAnalytics-AdaptiveGroups'. In the first instance (line 22), it's plain text in a tag, but in the second instance (line 323), it's wrapped in
tags. For consistency, both instances should use the same formatting.