VAULT-32201 release notes for product usage reporting #28904
Merged
+159
−38
Conversation
This file contains 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
github-actions
bot
added
the
hashicorp-contributed-pr
|
CI Results: |
|
Build Results: |
akshya96
reviewed
Nov 14, 2024
| | Known Issue (0.7.0+) | [Manual entity merges fail](/vault/docs/upgrading/upgrade-to-1.16.x#manual-entity-merges-sent-to-a-pr-secondary-cluster-are-not-persisted-to-storage) | | ||
| | Known Issue (1.16.7-1.16.8) | [Some values in the audit logs not hmac'd properly](/vault/docs/upgrading/upgrade-to-1.16.x#client-tokens-and-token-accessors-audited-in-plaintext) | | ||
| | New default (1.16.13) | [Vault product usage metrics reporting](/vault/docs/enterprise/license/product-usage-reporting) | | ||
| | Deprecation (1.16.13) | [`default_report_months` is deprecated for the `sys/internal/counters` API](/vault/docs/upgrading/upgrade-to-1.18.x#activity-log-changes) | |
There was a problem hiding this comment.
Should we update the upgrade docs for 1.16, 1.17 as well? Asking because the link used here is for 1.18. Should we replace it with 1.16 link?
akshya96
reviewed
Nov 14, 2024
| | Known Issue (1.17.3-1.17.4) | [Some values in the audit logs not hmac'd properly](/vault/docs/upgrading/upgrade-to-1.17.x#client-tokens-and-token-accessors-audited-in-plaintext) | | ||
| | Known Issue (1.17.0-1.17.5) | [Cached activation flags for secrets sync on follower nodes are not updated](/vault/docs/upgrading/upgrade-to-1.17.x#cached-activation-flags-for-secrets-sync-on-follower-nodes-are-not-updated) | | ||
| | New default (1.17.9) | [Vault product usage metrics reporting](/vault/docs/enterprise/license/product-usage-reporting) | | ||
| | Deprecation (1.17.9) | [`default_report_months` is deprecated for the `sys/internal/counters` API](/vault/docs/upgrading/upgrade-to-1.18.x#activity-log-changes) | |
There was a problem hiding this comment.
Should we update the upgrade docs for 1.16, 1.17 as well? Asking because the link used here is for 1.18. Should we replace it with 1.17 link?
There was a problem hiding this comment.
Hmm, that's a good point -- it only applies in the latest releases but I think you're probably right. Let me make this update!
akshya96
approved these changes
Nov 14, 2024
6 tasks
VioletHynes
added a commit
that referenced
this pull request
Nov 14, 2024
* VAULT-32201 release notes for product usage reporting * Add note about default report months * Better release notes
6 tasks
VioletHynes
added a commit
that referenced
this pull request
Nov 14, 2024
* VAULT-32201 release notes for product usage reporting * Add note about default report months * Better release notes
6 tasks
VioletHynes
added a commit
that referenced
this pull request
Nov 14, 2024
* VAULT-32201 release notes for product usage reporting * Add note about default report months * Better release notes
6 tasks
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.
Description
Companion PR for #28858 now that we're confident it's going in these three releases. It'll need to be backported together manually with that PR for 1.17 and 1.16. I'll do that once this is approved and merged etc.
TODO only if you're a HashiCorp employee
to N, N-1, and N-2, using the
backport/ent/x.x.x+entlabels. If this PR is in the CE repo, you should only backport to N, using thebackport/x.x.xlabel, not the enterprise labels.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.