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

feat(provider): Support worker filter on dynamic host catalogs #626

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

hugoghx
Copy link
Contributor

@hugoghx hugoghx commented Oct 1, 2024

No description provided.

@hugoghx hugoghx self-assigned this Oct 1, 2024
@hugoghx

This comment was marked as resolved.

@hugoghx hugoghx requested a review from louisruch October 9, 2024 14:28
@hugoghx hugoghx marked this pull request as ready for review October 9, 2024 14:28
go.mod Show resolved Hide resolved
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.

LGTM for the most part one question on HCP Only vs Enterprise Only wording.

We will also need to include a changelog entry for the addition of worker filter

@@ -94,6 +94,7 @@ resource "boundary_host_catalog_plugin" "azure_example" {
- `plugin_name` (String) The name of the plugin that should back the resource. This or plugin_id must be defined.
- `secrets_hmac` (String) The HMAC'd secrets value returned from the server.
- `secrets_json` (String, Sensitive) The secrets for the host catalog. Either values encoded with the "jsonencode" function, pre-escaped JSON string, or a file:// or env:// path. Set to a string "null" to clear any existing values. NOTE: Unlike "attributes_json", removing this block will NOT clear secrets from the host catalog; this allows injecting secrets for one call, then removing them for storage.
- `worker_filter` (String) HCP Only. A filter used to control which PKI workers can handle dynamic host catalog requests.
Copy link
Contributor

Choose a reason for hiding this comment

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

Interesting I wonder if we need to update our other usage of HCP Only - this is a relic of before we had self hosted. Perhaps we should align this with Enterprise-only as we did in Boundary. But perhpas worth starting a thread and taggin Anando from product on his thoughts

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah, I really only followed our current convention in these docs, but this is technically incorrect.

I suppose we could update it everywhere to say HCP and Boundary Enterprise only or something like this. @anando-chatterjee WDYT?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@hugoghx hugoghx force-pushed the hugo-dhc-workerfilter branch 2 times, most recently from fc7f471 to 4efc373 Compare October 17, 2024 14:37
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.

2 participants