Repository navigation
Conversation
This branch has not been deployed
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
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.
Closes #405
Related: AAP-99739 and upstream Syntara PR #1193. The upstream PR is open. After it merges, the workaround remains useful until a product release containing the fix is available.
Solution
Apply the temporary structured-output workaround automatically from the existing Infrastructure | Automation Orchestrator | Install job, using its existing OpenShift credential. For object response schemas on Task Agents without tools, the workaround prompts for JSON text, validates it against the schema, and retries up to three times. If no response is valid, the step fails. Other agent configurations retain their existing path.
What changed
workshop_prompt_jsonin its metadata.ao_workaround_state: absentremoves the overlay. Once deployed overlays have been removed, the isolated workaround block and directory can be deleted from this project.kubectl; no standalone rollout inventory, playbook, or extra execution environment is needed. Document the lifecycle and retain focused integration tests.Validation
AO Execution Environmentimage. They cover apply, idempotence, removal after a simulated backend upgrade, check mode, version guards, conflicting configuration, and invalid state.ansible-playbook -i localhost, infrastructure/ao/install.yml --syntax-check,ansible-lint infrastructure/ao/install.yml infrastructure/setup.yml, and Black checks passed.Limits
This is an operator-unmanaged overlay, not a product fix. It is pinned to the tested AO backend image and source; upgrades or reconciliation can remove or invalidate it. Rollout and removal restart workers. Schema validity does not guarantee factual correctness, and sequential tests do not establish behavior under load.