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

Allow requester/watchers to see step outputs #201

Open
rclsilver opened this issue Dec 2, 2020 · 2 comments
Open

Allow requester/watchers to see step outputs #201

rclsilver opened this issue Dec 2, 2020 · 2 comments
Labels
enhancement New feature or request

Comments

@rclsilver
Copy link
Contributor

Is your feature request related to a problem? Please describe.
We use uTask in our deployment software. We store some technical informations in step results but watchers are not allowed to see data.

Describe the solution you'd like
For a specific template (or maybe specific step), I would like a flag which allows watcher to see output.

Describe alternatives you've considered
The only alternative is to set all watchers as resolver...

@rclsilver rclsilver added the enhancement New feature or request label Dec 2, 2020
@rbeuque74 rbeuque74 changed the title Allow watchers to see step outputs Allow requester/watchers to see step outputs Dec 4, 2020
@rbeuque74
Copy link
Member

Hello,
Thanks for the suggestion. I renamed it as the requester is also not allowed to see the output.
This was a decision we made a long time ago, because we didn't want that requester can see the output of our internal business processes.

Having access to step output is only intended for debugging purposes.
If you want to expose some informations from the steps output to the requester/watchers, I guess you should add them as result_format (https://github.com/ovh/utask#basic-properties) so requester/watchers can see it.

In the mean time, I think that something we should have in the configuration, either on the template or in the global configuration of the instance: if the instance admin knows that all step output are not critical, or safe for the requester to look into, he should be able to disclose them, without redeclaring everything in the result_map

@rclsilver
Copy link
Contributor Author

In my case, it can be for debug purpose because when a step is blocked, requester/watchers could see details in step output. At this moment, output result_map is not yet computed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants