You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
st2 execution get doesn't print action.ref for non-workflow actions #4739
Found out too that this is how the st2 execution list command sets up its defaults for the --attr param. Guessing this was missed when doing some refactoring.
Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically marking is as stale. If this issue is not relevant or applicable anymore (problem has been fixed in a new version or similar), please close the issue or let us know so we can close it. On the contrary, if the issue is still relevant, there is nothing you need to do, but if you have any additional details or context which would help us when working on this issue, please include it as a comment to this issue.
Activity
nmaludy commentedon Jul 12, 2019
Debugging this, i found that the displayed attributes are hard coded in the
--attrargument definition: https://github.com/StackStorm/st2/blob/master/st2client/st2client/commands/action.py#L299Instead of using the
display_attributesproperty of each command: https://github.com/StackStorm/st2/blob/master/st2client/st2client/commands/action.py#L242-L243I'm thinking the proper fix is to change the default for the
--attrargument to bedefault=self.display_attributes.nmaludy commentedon Jul 12, 2019
Found out too that this is how the
st2 execution listcommand sets up its defaults for the--attrparam. Guessing this was missed when doing some refactoring.https://github.com/StackStorm/st2/blob/master/st2client/st2client/commands/action.py#L1106
Fixed StackStorm#4739. st2 cli now prints action ref for various comm…
stale commentedon Oct 10, 2019
Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically marking is as stale. If this issue is not relevant or applicable anymore (problem has been fixed in a new version or similar), please close the issue or let us know so we can close it. On the contrary, if the issue is still relevant, there is nothing you need to do, but if you have any additional details or context which would help us when working on this issue, please include it as a comment to this issue.
nmaludy commentedon Oct 10, 2019
PR is still open