Michael Li
63a1d9a5e9
* fix: Modify error message * refact: Rename keys for consistency * fix: Use scope_id in boundary_scope The examples for the boundary_scope data source suggest to use `parent_scope_id`, but the provider is actually expecting `scope_id`.
40 lines
1008 B
Markdown
40 lines
1008 B
Markdown
---
|
|
page_title: "boundary_scope Data Source - terraform-provider-boundary"
|
|
subcategory: ""
|
|
description: |-
|
|
The scope data source allows you to discover an existing Boundary scope by name.
|
|
---
|
|
|
|
# boundary_scope (Data Source)
|
|
|
|
The scope data source allows you to discover an existing Boundary scope by name.
|
|
Please note that the Global scope will always have an id of "global", and does not need to be discovered with this data source.
|
|
|
|
## Example Usage
|
|
|
|
```terraform
|
|
# Retrieve the ID of a Boundary project
|
|
data "boundary_scope" "org" {
|
|
name = "SecOps"
|
|
scope_id = "global"
|
|
}
|
|
|
|
data "boundary_scope" "project" {
|
|
name = "2111"
|
|
scope_id = data.boundary_scope.id
|
|
}
|
|
```
|
|
|
|
<!-- schema generated by tfplugindocs -->
|
|
## Schema
|
|
|
|
### Required
|
|
|
|
- `name` (String) The name of the scope to retrieve.
|
|
- `scope_id` (String) The parent scope ID that will be queried for the scope.
|
|
|
|
### Read-Only
|
|
|
|
- `description` (String) The description of the retrieved scope.
|
|
- `id` (String) The ID of the retrieved scope.
|