Product usage reporting docs #28858
Merged
Product usage reporting docs #28858
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
VioletHynes
commented
Nov 7, 2024
| @@ -456,6 +465,11 @@ | |||
| }, | |||
| { | |||
| "title": "<code>sentinel</code>", | |||
| "badge": { | |||
There was a problem hiding this comment.
Unrelated to my PR but this should be there since it's an enterprise feature.
|
CI Results: |
|
Build Results: |
yhyakuna
reviewed
Nov 7, 2024
yhyakuna
approved these changes
Nov 9, 2024
6 tasks
6 tasks
6 tasks
VioletHynes
added a commit
that referenced
this pull request
Nov 14, 2024
* First draft of product usage reporting docs * Table data, fix issues * Changelog
6 tasks
VioletHynes
added a commit
that referenced
this pull request
Nov 14, 2024
* First draft of product usage reporting docs * Table data, fix issues * Changelog
6 tasks
VioletHynes
added a commit
that referenced
this pull request
Nov 15, 2024
…28918) * VAULT-32201 release notes for product usage reporting (#28904) * VAULT-32201 release notes for product usage reporting * Add note about default report months * Better release notes * Product usage reporting docs (#28858) * First draft of product usage reporting docs * Table data, fix issues * Changelog * mistakes * Update website/content/docs/upgrading/upgrade-to-1.16.x.mdx Co-authored-by: divyaac <[email protected]> --------- Co-authored-by: divyaac <[email protected]>
VioletHynes
added a commit
that referenced
this pull request
Nov 15, 2024
…28917) * Product usage reporting docs (#28858) * First draft of product usage reporting docs * Table data, fix issues * Changelog * VAULT-32201 release notes for product usage reporting (#28904) * VAULT-32201 release notes for product usage reporting * Add note about default report months * Better release notes * Update website/content/docs/upgrading/upgrade-to-1.16.x.mdx Co-authored-by: divyaac <[email protected]> * Update website/content/docs/upgrading/upgrade-to-1.17.x.mdx Co-authored-by: divyaac <[email protected]> --------- Co-authored-by: divyaac <[email protected]>
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
These are the docs for product usage reporting, and the changelog for the feature.
There was no 1.19 release notes page available at the time of writing, but it would need to be added later. Further, if we wanted to backport this to a minor release, we'd need to add a release note page for that, too, as we do not usually backport major changes like this.
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.