* 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
* chore: update provider.go to latest SDK
* chore: update resource_group.go to latest SDK
* chore: update resource_host_catalog.go to latest SDK
* chore: update resource_project.go to latest SDK
* chore: update resource_role.go to latest SDK
* chore: fix group resource to use project client
* chore: update resource_users.go to latest SDK
* chore: update resource_group_test.go to latest SDK
* chore: refactor resource_host_catalog_test.go to latest sdk
* chore: refactor resource_project_test.go to latest sdk
* chore: refactor resource_user_test.go to latest sdk
* chore: update to latest SDK usage
* update to use latest test controller
* feat: make project_id optional and override scope if set
* test: test org and project level group creation
* chore: pass around authToken info for using principal ID in setting grant scope
* build: update deps