Repository navigation
feat(onprem): support deployment responses and Ansible task trees - #27
Merged
Merged
Conversation
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.
On-premises apps were rejected by the frontend's redeploy and metrics validators, and Ansible callbacks appeared under generic resource groups. Accept compute=onprem and display an Ansible task view with full task names, state, failure details, and deleted tasks. Unsupported monitoring is shown as a normal response.
The existing deployment endpoints, polling behavior, AWS resource categories, and stage navigation remain intact. Received-task completion is explicitly separated from overall deployment progress; no VM topology is inferred.
Validation: