fix: Address conflict in boundary_scope data source schema (#492)

* 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`.
This commit is contained in:
Michael Li authored and GitHub committed 2023-10-24 15:45:07 -04:00
1 parent 54fd626ae5
commit 63a1d9a5e9
6 files changed
+18 -18

No files matched your search

+4 -4
View File
@@ -15,13 +15,13 @@ Please note that the Global scope will always have an id of "global", and does n
```terraform
# Retrieve the ID of a Boundary project
data "boundary_scope" "org" {
name = "SecOps"
parent_scope_id = "global"
name = "SecOps"
scope_id = "global"
}
data "boundary_scope" "project" {
name = "2111"
parent_scope_id = data.boundary_scope.id
name = "2111"
scope_id = data.boundary_scope.id
}
```