-
Notifications
You must be signed in to change notification settings - Fork 54
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
base: main
Are you sure you want to change the base?
Conversation
00b11db
to
2a1ba22
Compare
This comment was marked as resolved.
This comment was marked as resolved.
acd3e53
to
9d5d0ec
Compare
There was a problem hiding this 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. |
There was a problem hiding this comment.
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
There was a problem hiding this comment.
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?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
fc7f471
to
4efc373
Compare
4efc373
to
dd817de
Compare
No description provided.