ResiLien
/
terraform
2
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
terraform/website/source/docs/providers/cloudstack/r/template.html.markdown

82 lines
2.6 KiB
Markdown
Raw Normal View History

Adding docs for the new resource...
2015-04-12 10:52:29 +02:00
---
layout: "cloudstack"
page_title: "CloudStack: cloudstack_template"
sidebar_current: "docs-cloudstack-resource-template"
description: |-
Registers an existing template into the CloudStack cloud.
---
Update cloudstack provider
2017-04-10 18:15:08 +02:00
# cloudstack_template
Adding docs for the new resource...
2015-04-12 10:52:29 +02:00
Registers an existing template into the CloudStack cloud.
## Example Usage
Update cloudstack provider
2017-04-10 18:15:08 +02:00
```hcl
Adding docs for the new resource...
2015-04-12 10:52:29 +02:00
resource "cloudstack_template" "centos64" {
website/docs: Run `terraform fmt` on code examples (#12075) * docs/vsphere: Fix code block * docs: Convert `...` to `# ...` to allow `terraform fmt`ing * docs: Trim trailing whitespace * docs: First-pass run of `terraform fmt` on code examples
2017-02-18 23:48:50 +01:00
name = "CentOS 6.4 x64"
format = "VHD"
Adding docs for the new resource...
2015-04-12 10:52:29 +02:00
hypervisor = "XenServer"
website/docs: Run `terraform fmt` on code examples (#12075) * docs/vsphere: Fix code block * docs: Convert `...` to `# ...` to allow `terraform fmt`ing * docs: Trim trailing whitespace * docs: First-pass run of `terraform fmt` on code examples
2017-02-18 23:48:50 +01:00
os_type = "CentOS 6.4 (64bit)"
url = "http://someurl.com/template.vhd"
zone = "zone-1"
Adding docs for the new resource...
2015-04-12 10:52:29 +02:00
}
```
## Argument Reference
The following arguments are supported:
* `name` - (Required) The name of the template.
* `display_text` - (Optional) The display name of the template.
Refactor the use of names vs IDs for parameters referencing other TF resources We have a curtesy function in place allowing you to specify both a `name` of `ID`. But in order for the graph to be build correctly when you recreate or taint stuff that other resources depend on, we need to reference the `ID` and *not* the `name`. So in order to enforce this and by that help people to not make this mistake unknowingly, I deprecated all the parameters this allies to and changed the logic, docs and tests accordingly.
2016-04-11 17:14:19 +02:00
* `format` - (Required) The format of the template. Valid values are `QCOW2`,
`RAW`, and `VHD`.
Adding docs for the new resource...
2015-04-12 10:52:29 +02:00
* `hypervisor` - (Required) The target hypervisor for the template. Changing
this forces a new resource to be created.
* `os_type` - (Required) The OS Type that best represents the OS of this
template.
* `url` - (Required) The URL of where the template is hosted. Changing this
forces a new resource to be created.
Refactor the use of names vs IDs for parameters referencing other TF resources We have a curtesy function in place allowing you to specify both a `name` of `ID`. But in order for the graph to be build correctly when you recreate or taint stuff that other resources depend on, we need to reference the `ID` and *not* the `name`. So in order to enforce this and by that help people to not make this mistake unknowingly, I deprecated all the parameters this allies to and changed the logic, docs and tests accordingly.
2016-04-11 17:14:19 +02:00
* `project` - (Optional) The name or ID of the project to create this template for.
Changing this forces a new resource to be created.
Fixes #1: sets the rights values based on isUUID
2015-04-29 11:21:37 +02:00
* `zone` - (Required) The name or ID of the zone where this template will be created.
Adding docs for the new resource...
2015-04-12 10:52:29 +02:00
Changing this forces a new resource to be created.
* `is_dynamically_scalable` - (Optional) Set to indicate if the template contains
Refactor the use of names vs IDs for parameters referencing other TF resources We have a curtesy function in place allowing you to specify both a `name` of `ID`. But in order for the graph to be build correctly when you recreate or taint stuff that other resources depend on, we need to reference the `ID` and *not* the `name`. So in order to enforce this and by that help people to not make this mistake unknowingly, I deprecated all the parameters this allies to and changed the logic, docs and tests accordingly.
2016-04-11 17:14:19 +02:00
tools to support dynamic scaling of VM cpu/memory (defaults false)
Adding docs for the new resource...
2015-04-12 10:52:29 +02:00
* `is_extractable` - (Optional) Set to indicate if the template is extractable
(defaults false)
* `is_featured` - (Optional) Set to indicate if the template is featured
(defaults false)
* `is_public` - (Optional) Set to indicate if the template is available for
all accounts (defaults true)
* `password_enabled` - (Optional) Set to indicate if the template should be
password enabled (defaults false)
* `is_ready_timeout` - (Optional) The maximum time in seconds to wait until the
template is ready for use (defaults 300 seconds)
## Attributes Reference
The following attributes are exported:
* `id` - The template ID.
* `display_text` - The display text of the template.
* `is_dynamically_scalable` - Set to "true" if the template is dynamically scalable.
* `is_extractable` - Set to "true" if the template is extractable.
* `is_featured` - Set to "true" if the template is featured.
* `is_public` - Set to "true" if the template is public.
* `password_enabled` - Set to "true" if the template is password enabled.
* `is_ready` - Set to "true" once the template is ready for use.