IssueTracker

What you would like to accomplish:
A useful feature for deployment manager would be to be able to dump a YAML document/manifest containing the configurations for existing resources within a project.  This would allow non-deployment manager configurations to be more easily acquired/imported/codified for future use/managed deployments with deployment manager.

How this might work:
Make a REST or gcloud request against a resource/set of resources in a project and get a response containing a YAML manifest with the required configuration that would allow that resource to be created/acquired by deployment manager as-is.

Something like:
gcloud deployment-manager generate-manifest --project xxx
Output:
resources:
  - name: NAME_OF_RESOURCE
    type: TYPE_OF_RESOURCE
    properties:
      property-a: value
      property-b: value
      ...
      property-z: value
  - name: NAME_OF_RESOURCE2
    type: TYPE_OF_RESOURCE2
   ....

If applicable, reasons why alternative solutions are not sufficient:
* Not all configurations documented by the API methods apply to or are supported by deployment manager.  
* Sometimes there are deployment manager specific fields which are not part of the API spec.
* This could be a time-saver for acquiring the appropriate YAML format for existing resources which is otherwise a trial and error/manual job via API specs and published examples.

Other information (workarounds you have tried, documentation consulted, etc):
Some resources in the console UI have a REST representation of the resource available to view.  This is a useful starting point, but not all resources have this available.