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 }}
This repository was archived by the owner on Jul 24, 2018. It is now read-only.
A typical ops use-case when troubleshooting a problem is to inspect the current running configs of components. For example, when investigating a neutron issue, one would want to examine the neutron.conf being used in the environment.
My understanding is that the shipyard API GET /v1.0/renderedconfigdocs would not provide the documents as rendered by Helm (neutron.conf, nova.conf, etc).
If this is the case, then adding this sort of capability to shipyard is something I think would be useful for operations and general debugging.
A typical ops use-case when troubleshooting a problem is to inspect the current running configs of components. For example, when investigating a neutron issue, one would want to examine the neutron.conf being used in the environment.
My understanding is that the shipyard API
GET /v1.0/renderedconfigdocswould not provide the documents as rendered by Helm (neutron.conf, nova.conf, etc).If this is the case, then adding this sort of capability to shipyard is something I think would be useful for operations and general debugging.
@alanmeadows
@intlabs