Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix lastEventId tracking #546

Merged
merged 4 commits into from
Jul 22, 2022
Merged

fix lastEventId tracking #546

merged 4 commits into from
Jul 22, 2022

Conversation

michalskrivanek
Copy link
Member

  • core: remove redundant set
  • core: fix lastEventId tracking

due to singleton usage we may be reading wrong lastEventId, but it is
not really needed so let's siplify the logic and use the existing
AnsibleReturnValue for keeping track of it.
@michalskrivanek
Copy link
Member Author

/ost

1 similar comment
@michalskrivanek
Copy link
Member Author

/ost

Copy link
Member

@mnecas mnecas left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@michalskrivanek
Copy link
Member Author

/ost

@michalskrivanek
Copy link
Member Author

/ost

@mnecas mnecas mentioned this pull request Jul 22, 2022
Instead of parsing the current event we can reuse the same logic as used
for async playbooks, check the "status" artifact to see if ansible is
still running or not, and check if all events have been processed
we rely on this exact behavior of ansible-runner, let's document it
@michalskrivanek michalskrivanek merged commit 995f4a0 into master Jul 22, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants