* fix: Allow users to set OIDC maxAge value to 0 to require immediate reauth (#364)
* 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
* spelling: host_set_plugin exmaple to example
* Update target.md (#349)
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.
```
* feature: add worker_filter option to Boundary Credential Store Vault (#375)
* feature: add worker_filter option to Boundary Credential Store Vault
* Update changelog
* chore: update deps
* small fixes for cherry-picks
* downgrade hclog
---------
Co-authored-by: mocofound <aharness@hashicorp.com>
Co-authored-by: Steven Zamborsky <97125550+stevenzamborsky@users.noreply.github.com>
Co-authored-by: Louis Ruch <louisruch@gmail.com>
Boundary changes how the test harness is used in order to speed up its
tests. It now requires that a postgres docker container is started prior
to running the tests. This adds some make targets to start up the docker
image, using the same image as boundary.
* 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>
* 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
Timothy Messier
Lewis Cowper
Brian Flad
Paul Tyng
Randall Morey
Todd Knight