* 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>
* 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 test coverage for authenticating with recovery kms mechanism & oidc primary auth method
* Skip fetching default auth method when recovery_kms_hcl is set or the client token isn't null
* 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
* 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>
* add username password resource
* fix a few bugs in the tf code as well as complete tests with copied crypto code
* address PR comments
* clean up all of the hmac testing code
* remove plan only in test and fix some descriptions per PR
* 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
After moving to go-kms-wrapping V2, the Boundary Terraform Provider
did not load all KMS plugins resulting in an error when trying to
create a wrapper for any type other than aead:
Error: error reading wrappers from "recovery_kms_hcl":
Error configuring kms: plugin is nil
* feat: add managed group resource
* feat: add tests for managed group resource
* update go.sum
* update tests
* simplify the managed group resource
* use WithDefaultPasswordAuthMethodId
* Managed groups (#129)
* docs: update host catalog resource with correct value for type attribute
* build: add Makefile target for auto-generating docs
* bugfix: make OIDC account attribute for subject ForceNew
* docs: update auto-generated docs
* Add credential library resource for Vault (#114)
* Integrate with Vault to retrieve and manage per session credentials
Co-authored-by: Louis Ruch <louisruch@gmail.com>
* Update token/clientKey on hmac change (#125)
* Update token/clientKey on hmac change
* Update changelog
* Update docs
* Prep for 1.0.3
* v1.0.3
* Update terraform-plugin-sdk
* Fix Typo
* Adopt American spelling
* fix the parameter that is actually being sent as the auth method id
Co-authored-by: Jeff Malnick <malnick@gmail.com>
Co-authored-by: Louis Ruch <louisruch@gmail.com>
Co-authored-by: Jeff Mitchell <jeffrey.mitchell@gmail.com>
Co-authored-by: tf-release-bot <terraform@hashicorp.com>
Co-authored-by: Lewis Cowper <593574+lewiscowper@users.noreply.github.com>
* nits and updates
* OIDC auth method + get filter from attributes
* Add changelog
* Fix schema description
Co-authored-by: Riley Guerin <rileytg@users.noreply.github.com>
Co-authored-by: Louis Ruch <louisruch@gmail.com>
Co-authored-by: Jeff Mitchell <jeffrey.mitchell@gmail.com>
Co-authored-by: tf-release-bot <terraform@hashicorp.com>
Co-authored-by: Lewis Cowper <593574+lewiscowper@users.noreply.github.com>
* 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>
* Begin API updating
* Update scope and user providers
* Update group resource
* Update to TF plugin SDK v2
* Finish recovery KMS workflow
This also modifies groups tests to use it. It's easy to verify from the
controller output that it's being used since it causes warnings to be
printed.
* Finish porting group resource to proposed new paradigm
* Minor cleanup
* Allow specifying a particular token for auth
* base_url -> addr
* Add test using token
* Add set calls to Update
* Update SDK
* Update SDK
* Update user and scope
* Half of host catalog and some consolidation
* Finish host catalog
* Add host resource
* Add host set resource
* Update targets
* Some updates to newer API
* Start updating to response map standards
* Finish updating already ported resources to new paradigm
* Finish existing resource porting
* Update target to exercise default port
* Adapt target to using json.Number
* Add auth method and account resources