Manually update api specs to address known issues#73
Merged
Conversation
RoleUserAssignment now supports two schema variants: assignment by user ID and assignment by user Ansible ID (resource ID), using a oneOf structure. This change clarifies API usage and improves flexibility for role assignments.
Updated the gateway-schema.json to include 'triggers' as a required field alongside 'authenticator' and 'name'. This ensures that objects conforming to this schema must specify 'triggers'.
Coverage Report
File CoverageNo changed files found. |
Added 'x-ai-description' fields to multiple endpoints in controller-schema.json to provide concise, human-readable summaries of each API operation. This improves API documentation and assists with automated tooling and AI integrations.
jameswnl
approved these changes
Nov 19, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Manually address the following:
https://issues.redhat.com/browse/AAP-57162
https://issues.redhat.com/browse/AAP-56793
https://issues.redhat.com/browse/AAP-56792
https://issues.redhat.com/browse/AAP-56795
These changes should (in theory) line up with the fixes that will eventually come in from the service delivery teams as they auto-generate their specs. I manually applied these changes to fast track our ability to test/validate and to prepare for the upcoming testathon.
Note that this addresses https://issues.redhat.com/browse/AAP-58697