* 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`.
* feat: add target session recording support
- add new optional `enable_session_recording` field for enabling or disabling session recording
- add new optional `storage_bucket_id` field for setting the storage bucket for the target
- These new fields are applicable to Boundary HCP/ENT
### Considerations
- There is no test coverage yet until we add support for testing enterprise only features. Manually tested the changes
* feat: add storage bucket resource
- Create a new resource for storage bucket
- Add examples and docs for how to use new resource
- Tests added but they do not run on purpose and have not been validated yet because we cannot run tests for enterprise features yet. That will be addressed separately
## Considerations
- Even though only AWS can be supported today, still added the `pluginID` & `pluginName` fields so it's easy to extend once other plugin types are supported
- There is some logic around handling secrets sent to Boundary and validating secret HMAC changes that exist from `boundary_host_catalog_plugin` that was introduced in [PR-159](https://github.com/hashicorp/terraform-provider-boundary/pull/159). Used the same logic we've been using for that
* add initial prototype of self managed worker resource and associated tests
* Add self managed worker resource and associated tests
* Update internal/provider/resource_self_managed_worker.go
Accept suggested schema changes for tags
Co-authored-by: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com>
* add environment variable check for worker led auth testing
* change resource name from self_managed_worker to worker for consistency with the api
* update tag schemas, ensure all attributes have descriptions
* add generated docs for worker
* add examples for worker resource
* add examples for worker resource
* remove merge conflict
* Remove funtionality for reflecting tags in the schema
* remove unused attributes (all tags) from schema, updates tests to use 'boundary_worker' on resource checks
* update example for inclusion in the website docs
---------
Co-authored-by: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com>
* add initial prototype of self managed worker resource and associated tests
* Add self managed worker resource and associated tests
* Update internal/provider/resource_self_managed_worker.go
Accept suggested schema changes for tags
Co-authored-by: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com>
* add environment variable check for worker led auth testing
* change resource name from self_managed_worker to worker for consistency with the api
* update tag schemas, ensure all attributes have descriptions
* add generated docs for worker
* add examples for worker resource
* add examples for worker resource
* remove merge conflict
* Remove funtionality for reflecting tags in the schema
* remove unused attributes (all tags) from schema, updates tests to use 'boundary_worker' on resource checks
Co-authored-by: Johan Brandhorst-Satzkorn <johan.brandhorst@gmail.com>
* added static store plus single test
* revert gomod and gosum changes
* upgrade boundary version from 0.8.1 to 0.9.1
* merged 0.9.1 update and cleaned up test file
* added example for static store, cleanup store and testfile for PR
* update scope test to ignore auto_create_admin_role needed for static credential store test
* update schema function and test comment
* remove auto_create_admin_role in favor of depends_on, and remove all references to the former
* Deprecate target host_set_ids and credential_library_ids
* Update changelog
* Include the 'type' attribute in the boundary_target documentation example. (#88)
* Include the 'type' attribute in the example.
* run tfplugindocs to generate the new markdown with type attribute change included
Co-authored-by: grantorchard <go@hashicorp.com>
* Update examples
* Remove update-deps target...go get -u is generally not what you want and we want more targeted updates
* Go mod tidy
* Fix up tools
* Update docs
* Cleanup some of the repo, prep for release
* Rework docs to new registry structure
* Add docs generator tooling
* Generate the docs
* update deps
* docs: add docs generation command to readme
Co-authored-by: Jeff Malnick <malnick@gmail.com>
Michael Li
drewmullen
Mark Christopher WestandJim
grantorchard
Uruemu S Aganbi
stellarsquall
Elim Tsiagbey
Chris van Meer
Louis Ruch
mocofound
Timothy Messier
Hugo
hashicorp-copywrite[bot]
Damian Debkowski
Danielle
Peter Lindsten
DevOps RobandLouis Ruch
Edgaras
Jeff Mitchell
Jeff MalnickandLouis Ruch
Paul Tyng