-
Notifications
You must be signed in to change notification settings - Fork 198
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
Pass full command-line and use as transaction title #1824
Conversation
First three there should be pretty straight-forward; split those out in #1825. |
☔ The latest upstream changes (presumably aaccd48) made this pull request unmergeable. Please resolve the merge conflicts. |
Expand the set to include '/' and '=' since those don't need escaping in shells.
In the app, rebuild the exact command-line that the client used and pass that to the daemon to be used as the transaction title. Especially in transactions like `UpdateDeployment()`, we can avoid reverse-engineering what the original command used was. This will be used by the upcoming history feature to record the command-line used in the journal.
OK, this one is ready for review! |
bot, retest this please |
Not sure what's causing this error - giving it another retest!
|
bot, retest this please |
Whee, all green now! ✔️ |
Scanned over, and this LGTM! |
Expand the set to include '/' and '=' since those don't need escaping in shells. Closes: #1824 Approved by: rfairley
In the app, rebuild the exact command-line that the client used and pass that to the daemon to be used as the transaction title. Especially in transactions like `UpdateDeployment()`, we can avoid reverse-engineering what the original command used was. This will be used by the upcoming history feature to record the command-line used in the journal. Closes: #1824 Approved by: rfairley
@rh-atomic-bot retry |
Expand the set to include '/' and '=' since those don't need escaping in shells. Closes: #1824 Approved by: rfairley
In the app, rebuild the exact command-line that the client used and pass that to the daemon to be used as the transaction title. Especially in transactions like `UpdateDeployment()`, we can avoid reverse-engineering what the original command used was. This will be used by the upcoming history feature to record the command-line used in the journal. Closes: #1824 Approved by: rfairley
😕 @rh-atomic-bot retry |
I'm OK with this but...there won't be a (useful) command line for gnome-software for example. I guess though a lot of other automation agents are probably just going to end up executing the binary. |
In the app, rebuild the exact command-line that the client used and pass that to the daemon to be used as the transaction title. Especially in transactions like `UpdateDeployment()`, we can avoid reverse-engineering what the original command used was. This will be used by the upcoming history feature to record the command-line used in the journal. Closes: #1824 Approved by: rfairley
Yeah, I left the fallback heuristics in place in case some other client triggered us. All this is just extra sugar, not essential. My goal specifically here is to make it show up in the |
☀️ Test successful - status-atomicjenkins |
In the app, rebuild the exact command-line that the client used and pass
that to the daemon to be used as the transaction title. Especially in
transactions like
UpdateDeployment()
, we can avoid reverse-engineeringwhat the original command used was.
This will be used by the upcoming history feature to record the
command-line used in the journal.
Split out of #1813.