* update census to run less frequently
* Update internal/census/census_job.go
Co-authored-by: Michael Gaffney <mike@gaffney.cc>
* change nextrunin duration
---------
Co-authored-by: Michael Gaffney <mike@gaffney.cc>
* docs: Add default client port to domain model
* docs: Minor edit
* docs: Consolidate overlapping attributes
* docs: Make connections generic, add ENT/HCP
When using an alias, we automatically add a little
blurb to the end of the flag help. When not terminating
the flag help with a full stop, this looks a bit odd. Add
full stops to all the download flags for consistency.
Our systemd setup included both a controller and worker
configuration example, and a %i templated config file meant
to be used to determine which to use. For ease of use, merge
the two config files into a predictably named "boundary.hcl".
Occasionally, we see an error from the gldap test directory reported
during the shutdown/close of the directories listener. This update
should fix that issue.
The auth-tokens help command included a reference to
a non-existent auth-tokens create command. Replace the
default help and also add a helpful pointer to the authenticate
command.
* docs: update NormalizeSetData comments
Update comments for `NormalizeSetData` to include when `NormalizeSetData` could be useful and the non-obvious consequences of using it.
onUpdate for host catalog & host set make a call to the plugin to normalize attributes based in. This behavior was introduced [PR-2376](https://github.com/hashicorp/boundary/pull/2376) but was only applied on onUpdate. This created different data structures for onCreate calls and onUpdate calls.
This avoids a situation where teardown results in an error due to the
worker not accepting the connection (since the credentials are invalid).
Teardown is a best-effort way to avoid sessions that have long lifetimes
ending up having to wait for expiration before cleanup, but if we're
near expiration it doesn't really matter.
Fixes ICU-9633
This allows specifying multiple IDs in grants via an `ids` field, which
will eventually become the normal way to specify IDs. Internally, each
grant with multiple IDs turns into multiple ACL grants each with a
single ID; to make this distinction clearer and allow for better
separation of concerns an AclGrant type has been introduced, so really
multiple IDs in a Grant turn into multiple AclGrants.
The nice thing about doing it this way is that it becomes purely a
parsing concern; no actual validation logic has changed.
For backwards compatibility with grants already stored in roles, we do
not error out if `id` is specified. However, eventually we will simply
not support grants with `id` coming via the API; they will fail API
validation, such that new grants will require the use of the updated
`ids` field.
A follow-on PR will plumb this through the service handlers/API/CLI, but
I decided to do it in separate chunks to make reviewing easier, given
that they are easily separable into the internal and external aspects of
the change.
* Add CLI/API checks around using ID in grants (#3264)
* Plumb through some contexts to remove a lot of deprecated errors (#3268)
This moves the contents of the readme used for hashicorp/boundary on
docker.io/registry.hub.docker.com to a separate readme file from the one that
documents how to build docker images. It also makes some minor fixups
and updates the docker.io readme, must notably updating the minimum
version of postgres that boundary requires.
Michael MiltonandMichael Gaffney
Dan Heath
Stan Ryzhov
Michael Li
Todd
Irena RindosandDan Heath
Jim
Johan Brandhorst-Satzkorn
Cameron Perera
Elim Tsiagbey
Jeff Mitchell
PPacent
Louis Ruch
Mark Collao
Timothy Messier