* 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
During terraform update, the default worker filter option used is the `DefaultBucketName` instead of `DefaultWorkerFilter`. Update it to use the correct option
* 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
Michael Li
hashicorp-copywrite[bot]
oss-core-libraries-dashboard[bot]andhashicorp-copywrite[bot]
Damian Debkowski
Elim Tsiagbey