SubnetRouteTableAssocation cannot reference an existing SubnetId

[Simon Pasquier]

Currently the following template will fail because the SubnetRouteTableAssocation resource calls resource_by_refid() to look up the subnet.
{
  ...
  "Parameters" : {
    "SubnetId" : {
      "Type" : "String",
      "Description" : "Id of an existing subnet"
    }
  }
  ...
  "Resources": {
    "myRouteTableAssoc": {
      "Type" : "AWS::EC2::SubnetRouteTableAssocation",
      "Properties" : {
        "SubnetId" : { "Ref" : "SubnetId" },
        "RouteTableId" : { "Ref" : "myRouter" }
      }
    },
   ...
}

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/35230

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/35230
Committed: http://github.com/openstack/heat/commit/4c1adb4c83f2f393dfb6a0460a8ecc3f14cd9b50
Submitter: Jenkins
Branch: master

commit 4c1adb4c83f2f393dfb6a0460a8ecc3f14cd9b50
Author: Steve Baker <email address hidden>
Date: Tue May 21 10:01:16 2013 +1200

    Rework associations from vpc to quantum resources.

    Metadata cannot be used to store the relationships between VPC
    resources and the underlying quantum resources, since this prevents
    VPC or Subnet refs from being passed in as parameters.

    This rework results in no state being stored in metadata. Route table
    relationships are inferred from the template. An assumption is made that
    the quantum router associatiated with the VPC will have the same name
    as the quantum net. The easiest way of ensuring that is to creat the VPC
    in a different Heat stack.

    Fixes bug: #1165050
    Fixes bug: #1165056
    Fixes bug: #1166779
    Fixes bug: #1166787

    Change-Id: I6fb087bfc63ed13703089a16ed57858e6911b7d8