-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
Show Current Month When Future Month Start Date is Provided #28042
Conversation
We should add a changelog for this :) |
CI Results: |
Build Results: |
changelog/28042.txt
Outdated
@@ -0,0 +1,3 @@ | |||
```release-note:bug | |||
activity: The sys/internal/counters/activity endpoint will return current month data when the start_date parameter is set to a future date. |
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.
activity: The sys/internal/counters/activity endpoint will return current month data when the start_date parameter is set to a future date. | |
activity: Fixed issue where sys/internal/counters/activity endpoint would not return current month data when the end_date parameter is set to a future date. |
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.
Some of this is subjective wording, but it should be end_date
, not start_date
. Feel free to take just the end_date
fix
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.
Looks good! The only thing we should definitely change before merging is the typo of start_date
to end_date
in the changelog (suggestion given for easy application to PR)
Thanks for the quick fix on this, and the awesome coverage!
* Show current month data * Added changelog * Edited changelog
* Handle Query Updates (#27547) * Simplify handle query to return updated estimation values * Added changelog * remove comment * Revert "Simplify handle query to return updated estimation values" This reverts commit b67969c. * temp * Revert "temp" This reverts commit 4932979. * CE files handle query update * Revert "CE files handle query update" This reverts commit 8dafa2d. * CE Changes * Delete vault/external_tests/upgrade_testing/upgrade_testing_binary/upgrade_test.go * Sort namespaces, mounts, and clients before adding them to HLL (#28062) * sort namespaces and mounts before adding them * also sort clients * add comments * pr comment fixes * changelog * changelog update * cleanup after handlequery changes (#27776) * Show Current Month When Future Month Start Date is Provided (#28042) * Show current month data * Added changelog * Edited changelog * Client Count Docs Updates/Cleanup (#27862) * Docs changes * More condensation of docs * Added some clarity on date ranges * Edited wording' * Added estimation client count info * Update website/content/api-docs/system/internal-counters.mdx Co-authored-by: miagilepner <mia.epner@hashicorp.com> --------- Co-authored-by: miagilepner <mia.epner@hashicorp.com> --------- Co-authored-by: divyaac <divya.chandrasekaran@hashicorp.com>
Description
ENT PR :
https://github.com/hashicorp/vault-enterprise/pull/6427
Adjusts the query response to include current month data when endTime = future date. Once this is approved, I will make a subsequent CE PR.
TODO only if you're a HashiCorp employee
getting backported to N-2, use the new style
backport/ent/x.x.x+ent
labelsinstead of the old style
backport/x.x.x
labels.the normal
backport/x.x.x
label (there should be only 1).of a public function, even if that change is in a CE file, double check that
applying the patch for this PR to the ENT repo and running tests doesn't
break any tests. Sometimes ENT only tests rely on public functions in CE
files.
in the PR description, commit message, or branch name.
description. Also, make sure the changelog is in this PR, not in your ENT PR.