* feat(proj-alias): support project scoped alias via suffixes
* fix: generate resouce docs using make gen
* fix: address review comments
* chore: make gen changes
* fix(proja-alias): validate scope id before calling remove alias suffix
* fix: filter unknown scopes in validation
* feat(password credential): Add password credential type support
* build(deps): upgrade Boundary to v0.21.0 and update dependencies
* chore: update go.mod and go.sum from main
* Dependency cleanup
This resource creates a static "Username, Password & Domain" credential in
Boundary.
The "username" field is required. It can also contain the domain in one of two
formats:
- "username@domain.com"
- "domain.com\username"
The "password" field is required.
The "domain" field is optional but the domain data itself is required (ie. it
must be provided as part of the username or in the dedicated "domain" field)
Co-authored-by: April-May <18632637+AprilMay0@users.noreply.github.com>
* docs: separate worker and controller led resources
* docs: change title for consistency
* docs: make docs
* chore: use unique names for workers and add an 'Example Usage' section
Update example for dynamic credential for storage bucket to include `disable_credential_rotation` attribute. `disable_credential_rotation` needs to be set to true when configuring dynamic credentials
* feat(oidc): OIDC Prompt Support
Boundary OIDC method does not currently support passing in prompts during authentication. This change adds the capability of passing OIDC prompts. Prompts are optional OIDC parameters that determine the behaviour of the authentication server: https://openid.net/specs/openid-connect-core-1_0.html#AuthRequest
Add new optional `prompts` option to `boundary_auth_method_oidc` resource. `prompts` option are optional OIDC parameters that determine the behavior of the authentication server.
* 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
* fix: Allow users to set OIDC maxAge value to 0 to require immediate reauth
Previously, setting 0 as a value for maxAge in an OIDC resource block would not update Boundary, as it was getting treated as a nil value in the provider.
This fix addresses that issue, ensuring that both setting the value to 0 will require immediate reauthorisation, as well as removing the maxAge paramater defaulting the reauth time length to the TTL of the chose OIDC provider
* Update doc strings, fix imports, and run go generate
* add changes to CHANGELOG
* chore: point to boundary ldap bits
* refactor (test): common auth method test funcs
* chore (deps): add gldap for test ldap directory
* feature: add LDAP auth-method, accounts and managed groups support
Update docs for Target resource removing `scope_id` from `boundary_host` resources to prevent error
```
╷
│ Error: Unsupported argument
│
│ on main.tf line 79, in resource "boundary_host" "foo":
│ 79: scope_id = boundary_scope.project.id
│
│ An argument named "scope_id" is not expected here.
```
* 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>
Bharath Gajjala
richardtrinh1
Amit Kotagi
Ryan Derr
Andrew Gaffney
Rayenn Hamrouni
Robin Beck
HugoandApril-May
dependabot[bot]andJohan Brandhorst-Satzkorn
Louis Ruch
Bruno Schaatsbergen
Todd
daniandDanielle Miu
Jeff Mitchell
Elim Tsiagbey
prsekar
Damian Debkowski
Michael Li
Mark Christopher WestandJim
Uruemu S Aganbi
Chris van Meer
Dan Heath
Michael Milton
mocofound
Steven Zamborsky
grantorchardandJohan Brandhorst-Satzkorn
Timothy Messier
Hugo
Irena Rindos