Skip to content

Added message deprecation info#527

Merged
mraineri merged 1 commit intomainfrom
Fix500-Message-Deprecation-Info
Mar 6, 2026
Merged

Added message deprecation info#527
mraineri merged 1 commit intomainfrom
Fix500-Message-Deprecation-Info

Conversation

@mraineri
Copy link
Copy Markdown
Contributor

Fix #500

Some sample output for the changes...

In the message summary table, using parenthesis to show version added/deprecated info in the same style as properties in the schema guide docs:

| [AccessForbidden](#Base-AccessForbidden) *(v1.20+, deprecated v1.22)* | Critical | Indicates that the request contained valid credentials, but the user does not have the necessary privileges to perform the requested operation. |

In the message details, put the deprecation notice after the descriptions:

### AccessForbidden<a id="Base-AccessForbidden"/>

Indicates that the request contained valid credentials, but the user does not have the necessary privileges to perform the requested operation.

* This message shall indicate that the request contained valid credentials, but the user does not have the necessary privileges to perform the requested operation.

*Deprecated in v1.22 and later.  This message was deprecated in favor of the existing `InsufficientPrivilege` message.*

Version Added: v1.20

Severity: Critical

Resolution: Resubmit the request with credentials that contain the necessary privileges to perform the requested operation.

Message and Arguments: "Forbidden."

Signed-off-by: Mike Raineri <michael.raineri@dell.com>
@mraineri mraineri added the Registry Doc Generator registry-doc-generator label Feb 26, 2026
@mraineri mraineri merged commit 1567f70 into main Mar 6, 2026
2 checks passed
@mraineri mraineri deleted the Fix500-Message-Deprecation-Info branch March 6, 2026 20:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Registry Doc Generator registry-doc-generator

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Include deprecation information in generated registry documentation

1 participant