github.com/bradfeehan/terraform@v0.7.0-rc3.0.20170529055808-34b45c5ad841/website/source/docs/providers/ovh/r/vrack_publiccloud_attachment.html.markdown (about)

     1  ---
     2  layout: "ovh"
     3  page_title: "OVH: vrack_publiccloud_attachment"
     4  sidebar_current: "docs-ovh-resource-vrack-publiccloud-attachment"
     5  description: |-
     6    Attach an existing PublicCloud project to an existing VRack.
     7  ---
     8  
     9  # ovh_vrack\_publiccloud\_attachment
    10  
    11  Attach an existing PublicCloud project to an existing VRack.
    12  
    13  ## Example Usage
    14  
    15  ```
    16  resource "ovh_vrack_publiccloud_attachment" "attach" {
    17    vrack_id   = "12345"
    18    project_id = "67890"
    19  }
    20  ```
    21  
    22  ## Argument Reference
    23  
    24  The following arguments are supported:
    25  
    26  * `vrack_id` - (Required) The id of the vrack. If omitted, the `OVH_VRACK_ID`
    27      environment variable is used.
    28  
    29  * `project_id` - (Required) The id of the public cloud project. If omitted,
    30      the `OVH_VRACK_ID` environment variable is used.
    31  
    32  ## Attributes Reference
    33  
    34  The following attributes are exported:
    35  
    36  * `vrack_id` - See Argument Reference above.
    37  * `project_id` - See Argument Reference above.
    38  
    39  ## Notes
    40  
    41  The vrack attachment isn't a proper resource with an ID. As such, the resource id will
    42  be forged from the vrack and project ids and there's no correct way to import the
    43  resource in terraform. When the resource is created by terraform, it first checks if the
    44  attachment already exists within OVH infrastructure; if it exists it set the resource id
    45  without modifying anything. Otherwise, it will try to attach the vrack with the public
    46  cloud project.