|
| 1 | +--- |
| 2 | +page_title: "spectrocloud_resource_limit Resource - terraform-provider-spectrocloud" |
| 3 | +subcategory: "" |
| 4 | +description: |- |
| 5 | + |
| 6 | +--- |
| 7 | + |
| 8 | +# spectrocloud_resource_limit (Resource) |
| 9 | + |
| 10 | + |
| 11 | + |
| 12 | +You can learn more about managing resource limit in Palette by reviewing the [Default Resource Limit](https://docs.spectrocloud.com/tenant-settings/palette-resource-limits/?utm_source=palette&utm_medium=product2docs) guide. |
| 13 | + |
| 14 | +~> The resource_limit resource enforces a resource limit in Palette. By default, a resource limit is configured in Palette with default values. Users can update the resource limit settings as per their requirements. When a spectrocloud_resource_limit resource is destroyed, the resource limits will revert to the Palette default settings. |
| 15 | + |
| 16 | +## Example Usage |
| 17 | + |
| 18 | +An example of managing an password policy in Palette. |
| 19 | + |
| 20 | +```hcl |
| 21 | +resource "spectrocloud_resource_limit" "resource_limit" { |
| 22 | + alert = 101 |
| 23 | + api_keys = 201 |
| 24 | + appliance = 6001 |
| 25 | + appliance_token = 201 |
| 26 | + application_deployment = 200 |
| 27 | + application_profile = 200 |
| 28 | + certificate = 20 |
| 29 | + cloud_account = 355 |
| 30 | + cluster = 300 |
| 31 | + cluster_group = 50 |
| 32 | + cluster_profile = 2500 |
| 33 | + filter = 200 |
| 34 | + location = 100 |
| 35 | + macro = 6000 |
| 36 | + private_gateway = 100 |
| 37 | + project = 200 |
| 38 | + registry = 200 |
| 39 | + role = 100 |
| 40 | + ssh_key = 300 |
| 41 | + team = 100 |
| 42 | + user = 300 |
| 43 | + workspace = 60 |
| 44 | +} |
| 45 | +
|
| 46 | +## import existing resource limit |
| 47 | +#import { |
| 48 | +# to = spectrocloud_resource_limit.resource_limit |
| 49 | +# id = "5eea74e919f5e0d43fd3f316" // tenant-uid |
| 50 | +#} |
| 51 | +``` |
| 52 | + |
| 53 | +<!-- schema generated by tfplugindocs --> |
| 54 | +## Schema |
| 55 | + |
| 56 | +### Optional |
| 57 | + |
| 58 | +- `alert` (Number) The maximum number of alerts that can be created. Must be between 1 and 10,000. |
| 59 | +- `api_keys` (Number) The maximum number of API keys that can be generated. Must be between 1 and 10,000. |
| 60 | +- `appliance` (Number) The maximum number of appliances that can be managed. Must be between 1 and 50,000. |
| 61 | +- `appliance_token` (Number) The maximum number of appliance tokens that can be issued. Must be between 1 and 10,000. |
| 62 | +- `application_deployment` (Number) The maximum number of application deployments allowed. Must be between 1 and 10,000. |
| 63 | +- `application_profile` (Number) The maximum number of application profiles that can be configured. Must be between 1 and 10,000. |
| 64 | +- `certificate` (Number) The maximum number of certificates that can be managed. Must be between 1 and 10,000. |
| 65 | +- `cloud_account` (Number) The maximum number of cloud accounts that can be added. Must be between 1 and 10,000. |
| 66 | +- `cluster` (Number) The maximum number of clusters that can be created. Must be between 1 and 50,000. |
| 67 | +- `cluster_group` (Number) The maximum number of cluster groups that can be created. Must be between 1 and 10,000. |
| 68 | +- `cluster_profile` (Number) The maximum number of cluster profiles that can be configured. Must be between 1 and 10,000. |
| 69 | +- `filter` (Number) The maximum number of filters that can be defined. Must be between 1 and 10,000. |
| 70 | +- `location` (Number) The maximum number of locations that can be configured. Must be between 1 and 10,000. |
| 71 | +- `macro` (Number) The maximum number of macros that can be created. Must be between 1 and 10,000. |
| 72 | +- `private_gateway` (Number) The maximum number of private gateways that can be managed. Must be between 1 and 10,000. |
| 73 | +- `project` (Number) The maximum number of projects that can be created. Must be between 1 and 10,000. |
| 74 | +- `registry` (Number) The maximum number of registries that can be configured. Must be between 1 and 10,000. |
| 75 | +- `role` (Number) The maximum number of roles that can be assigned. Must be between 1 and 10,000. |
| 76 | +- `ssh_key` (Number) The maximum number of SSH keys that can be managed. Must be between 1 and 10,000. |
| 77 | +- `team` (Number) The maximum number of teams that can be created. Must be between 1 and 10,000. |
| 78 | +- `timeouts` (Block, Optional) (see [below for nested schema](#nestedblock--timeouts)) |
| 79 | +- `user` (Number) The maximum number of users that can be added. Must be between 1 and 10,000. |
| 80 | +- `workspace` (Number) The maximum number of workspaces that can be created. Must be between 1 and 10,000. |
| 81 | + |
| 82 | +### Read-Only |
| 83 | + |
| 84 | +- `id` (String) The ID of this resource. |
| 85 | + |
| 86 | +<a id="nestedblock--timeouts"></a> |
| 87 | +### Nested Schema for `timeouts` |
| 88 | + |
| 89 | +Optional: |
| 90 | + |
| 91 | +- `create` (String) |
| 92 | +- `delete` (String) |
| 93 | +- `update` (String) |
0 commit comments