Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add dynamic host plugin catalog/set #159

Merged
merged 30 commits into from
Jan 20, 2022
Merged

Add dynamic host plugin catalog/set #159

merged 30 commits into from
Jan 20, 2022

Conversation

jefferai
Copy link
Member

This migrates existing host resources to static type (adding an explicit static type and deprecating the non-typed version), and creates plugin types for host catalog and host set.

Note: proper operation (specifically attribute null handling) depend on some post-0.7.1 Boundary patches. We could release without these patches in a release of Boundary but there will be some unexpected behavior around setting attributes to null/empty.

@jefferai jefferai requested a review from jimlambrt November 28, 2021 00:22
internal/provider/resource_host_catalog_plugin.go Outdated Show resolved Hide resolved
internal/provider/resource_host_catalog_plugin.go Outdated Show resolved Hide resolved
internal/provider/resource_host_catalog_plugin.go Outdated Show resolved Hide resolved
internal/provider/resource_host_catalog_plugin_test.go Outdated Show resolved Hide resolved
internal/provider/resource_host_catalog_static.go Outdated Show resolved Hide resolved
internal/provider/resource_host_catalog_plugin.go Outdated Show resolved Hide resolved
Copy link

@vancluever vancluever left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Mostly observational changes and nits. At least one thing that @talanknight mentioned. Looks like some of these are repeated patterns so any action take should likely be applied through the whole PR.

Copy link
Contributor

@louisruch louisruch left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Took a quick look will still take another look once tests go green tomorrow, you should run make docs on this as well

.circleci/config.yml Show resolved Hide resolved
internal/provider/resource_host_catalog_plugin.go Outdated Show resolved Hide resolved
@jefferai jefferai requested a review from hugoghx December 21, 2021 16:33
Copy link
Contributor

@talanknight talanknight left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good! My only concern is about how we compare the json attributes in the DiffSuppressFunc for plugin catalogs and sets, but that might be due to my misunderstanding of how things are stored or when the comparison happens. Happy to discuss!

internal/provider/resource_host_catalog_plugin.go Outdated Show resolved Hide resolved
internal/provider/resource_host_catalog_plugin.go Outdated Show resolved Hide resolved
@jefferai jefferai requested a review from talanknight January 3, 2022 14:47
@louisruch louisruch merged commit 6b28ea2 into main Jan 20, 2022
@louisruch louisruch deleted the jeff-dynamic-hosts branch January 20, 2022 00:19
elimt added a commit that referenced this pull request Jun 22, 2023
- 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](#159). Used the same logic we've been using for that
elimt added a commit that referenced this pull request Jun 28, 2023
* 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](#159). Used the same logic we've been using for that
elimt added a commit that referenced this pull request Jun 28, 2023
* 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](#159). Used the same logic we've been using for that
grantorchard pushed a commit to grantorchard/terraform-provider-boundary that referenced this pull request Aug 28, 2023
* 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](hashicorp#159). Used the same logic we've been using for that
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants