Change-Id: I2696e3af9193e8da4184eb95d86b091e55e27299

Change-Id: I94a67a4da0942691d5a9253c646d7d3c09a8cbe6

This shows the files map for a given stack

Depends-On: I3198b6a7dc06648af24c198d39470f3b0d5d6f11
Change-Id: Ib7d033a660fe294bf3f7b42e4aa7020149ce24c1
blueprint: files-show

Now that there is a passing gate job, we can claim support for
Python 3.5 in the classifier. This patch also adds the convenience
py35 venv.

Change-Id: I3b8b68c4ec4904d1aee150e6158f9ff29c68ff7a

This change registers a "dot" formatter for the stack resource list
command. It generates the text for a graphviz dot diagram which can be
rendered as an image with this example usage:

  openstack stack resource list --format dot -n3 my_stack | dot -Tsvg -o my_stack.svg

Nested resources are fully supported by creating nodes for top-level
resources then linking stack resources to a subgraph representing the
nested stack.

Change-Id: I4b899287eaf818137d60cb278db2d86598aa6794

A command which prints failed resources in the stack to help debug
stack issues.

Failed resources are added by recursing from the top level stack into
failed nested stack resources. A failed nested stack resource is only
added to the failed list if it contains no failed resources so that the
user only sees root-cause failed resources.

As an added convenience to debugging deployment resources, deployment
outputs deploy_stdout and deploy_stderr are printed as well (the full
outputs are printed when --long is specified).

The output is a yamlish format where the key is a dot-delimited resource
name path and the value is a dict of resource information.

Change-Id: Ifa44175d8dbab2f7b62691b839e1696e3af7f4f3
Closes-Bug: #1585820