* Supress group name case sensitive matching
* Moved DiffSuppressFunc onto the string Elem schema so it's applied per-element instead of the list itself
* Updated the test as per the new recent changes made in the main branch
* review changes
---------
Co-authored-by: Abhishek Singh Tanwar <abhishek_ibm@dhcp-9-127-1-123.c4p-in.ibm.com>
* chore: Update make testacc to use boundary dev
Use boundary dev instead of test controller in order to get an enterprise cluster
* test: Update tests to use boundary dev cluster
- Set up environment variables via loadTestConfig
- Update testConfigWithRecovery to use recovery key from config
- Update testCOnfigWithoutAMPWCredentials to use boundary dev's auth method
* test: Update tests to use their own orgs
This is to address some test failures due to conflicts when creating resources within the same org.
* test: Enable tests that require boundary-enterprise
* chore: Update workflow to use boundary enterprise
* 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
* test: Remove redundant grant_scope_id
After the Grants refactor in Boundary, we no longer support using redundant grant scopes together.
Example: An org role with both 'children' and an individual project id specified as grant scopes.
* chore: Remove unused vars
* fix test config with ldap auth method bug
---------
Co-authored-by: dkanney <david.kanney@hashicorp.com>
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>
* chore: replace deprecated arguments in provider example
* chore: fix extra newline
* Revert "chore: fix extra newline"
This reverts commit cf2de60acfcf6c9499d0306243041f950a0851f6.
* Revert "chore: replace deprecated arguments in provider example"
This reverts commit 49a336f7684707edb36021eef7d11bb92e4fa1b4.
* chore: change example
* chore: update example in README
* chore: create a tests for the deprecated auth method
* 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.
* 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`.
During terraform update, the default worker filter option used is the `DefaultBucketName` instead of `DefaultWorkerFilter`. Update it to use the correct option
* 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
shadowdaoandClaude Sonnet 5.5
Michael Li
Louis Ruch
abhi99shek99andAbhishek Singh Tanwar
Bharath Gajjala
Amit Kotagi
Ryan Derr
Chandrasekhar GaddeandChandrasekhar Gadde
hashicorp-copywrite[bot]
Pradeep Sekar
Andrew Gaffney
oss-core-libraries-dashboard[bot]andhashicorp-copywrite[bot]
Rayenn Hamrouni
Michael Miltonanddkanney
Hugo
Bruno Schaatsbergen
Todd
daniandDanielle Miu
Jeff Mitchell
Damian Debkowski
Elim Tsiagbey
drewmullen
Jim
grantorchard