-
Notifications
You must be signed in to change notification settings - Fork 361
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
Add --ident option to process command #939
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I had this worry early on but then nothing ever seemed to come of it. Ultimately, I think this is a good idea.
We could add more things to the |
If you wanted, we could actually add the |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I believe this is most likely ok. I see ident
is already documented in the interface.run()
method(s). I've been trying to get this to work via the Python API to make sure it works that way, but I'm having some difficulty getting that working properly (probably usage error on my part, not a bug here).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
Pull request merge failed: Resource not accessible by integration |
recheck |
4 similar comments
recheck |
recheck |
recheck |
recheck |
recheck |
Pull request merge failed: Resource not accessible by integration |
This will allow users to write artifacts in a way that matches normal non-remote ansible-runner commands It makes the most sense to have the process --ident match the --ident value passed to transmit, but you do not have to. The intention is that this will be used by AWX so that jobs ran and processed on the same node will not write artifacts twice.
643893e
to
801d97c
Compare
801d97c
to
4cca621
Compare
Fixes #821
Below is my bash scripts where I emulate AWX behavior on hybrid nodes. I might document these in a repository sometime... maybe they would work for docs? Maybe not because I actually run them.
Long story short, this is how AWX works with a slight modification for how I think it should work, which is the added
--ident
option.Without this, you have 2 files for
overwrite/1/artifacts/rc
andoverwrite/1/artifacts/b20e75dd2a4049708f3ed10a73cad3cc/rc/
. So which one is the right one? I want to avoid that confusion. Ping @jbradberry