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
* 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
Jeff Malnick
Paul Tyng
Paul Tyng
Jeff Mitchell
Todd Knight