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

Add full_return to release notes #41356

Merged
merged 1 commit into from
May 22, 2017
Merged

Add full_return to release notes #41356

merged 1 commit into from
May 22, 2017

Conversation

whiteinge
Copy link
Contributor

What does this PR do?

Release notes docs.

What issues does this PR fix or reference?

#39452

@ghost
Copy link

ghost commented May 20, 2017

@whiteinge, thanks for your PR! By analyzing the history of the files in this pull request, we identified @terminalmage, @rallytime and @mirceaulinic to be potential reviewers.

Copy link
Contributor

@rallytime rallytime left a comment

Choose a reason for hiding this comment

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

I had two questions about this doc addition. Am I misunderstanding those examples?


An ``full_return`` argument has been added to the ``cmd`` and ``cmd_sync``
methods in ``LocalClient`` and ``RunnerClient`` which causes the return data
structure to include job meta data such as ``ret_code`` and ``success``.
Copy link
Contributor

Choose a reason for hiding this comment

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

Should this be retcode instead of ret_code?

I also don't see anything in the example return data in the examples below about the success key in the cmd.run return dicts.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yikes, thank you for the careful eye!

Fixed to retcode. And you're right there is no success -- I'm surprised there isn't a 1-to-1 between job returns on the CLI and on the event bus. 😕

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.

3 participants