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
Consider a configuration switch that will execute APBs in ansible verbose mode for debugging purposes. #822
Comments
|
I think that this should be a generic flag, that tells a bundle to run in verbose mode and the base for that bundle know's how to translate that? |
|
@shawn-hurley what do you mean generic flag? something other than a setting in the configmap? Was thinking something like |
|
I was thinking something like |
|
Ah right. That's more correct, I would just request that we update all of the flags so things remain consistent, which is probably 2 PRs. First: move from _apb -> _bundle, which means updating docs and images. Then add this flag in a follow up. |
|
Funny, I thought it would be cool to have an endpoint on the broker that could have it dump debug information as well. I'll formulate a better idea and create an issue for this scenario. |
|
execute ansible with |
|
|
See ansible |
|
During the IRC meeting just now, it was agreed that this should be a generic setting that is not ansible-specific. Lots of things have a verbose mode and could make use of this flag. Suggested actions:
|
|
Just wanted to point out in here. That one of the things I learned from the helm registry adapter experiment, creating Specs from scratch, is that it is possible for us to add (from the broker) this verbose flag as a parameter to all plans such that Service Bundle Developers would not have to explicitly add this as a parameter. Example: |
|
@djzager this looks very useful, how hard do you think it would be to implement this? |
|
Issues go stale after 90d of inactivity. Mark the issue as fresh by commenting If this issue is safe to close now please do so with /lifecycle stale |
|
/close |
|
@jmrodri: Closing this issue. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
Came up on the CEE call. SSIA.
The text was updated successfully, but these errors were encountered: