11 Commits (c8ee312ae2e145afdc28ac4abb16d68d1ac2000d)

Author	SHA1	Message	Date
Jeff Mitchell	feb3aea38f	Support multiple IDs in grants (#3263) ... 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)	3 years ago
Jeff Mitchell	18e59998e9	Add storage bucket worker filter handling	3 years ago
Jeff Mitchell	b2bab45c13	Port over changes (#3061) (#3062)	3 years ago
Todd	4d19d1cfc4	Remove metadata from feature manager (#3046)	3 years ago
Damian Debkowski	cabe362534	fix(handler): return targetId as hostId for cli edge case support (#2920)	3 years ago
Timothy Messier	e25b0e7888	fix(credentiallibraries): Fallback logic to support 0.11.x cli (#2910)	3 years ago
Johan Brandhorst-Satzkorn	3c29308673	chore: Add license headers to all files	3 years ago
Timothy Messier	e66ea15fef	fix(cli): Status code on api error ... When using the json output of the cli (`-format=json`), a successful call to the controller API would place the HTTP status code in the JSON as `status_code`. However, if there was an error from the API the status code would be placed in the JSON as `status`. In order to be consistent, this adds a `status_code` field to the error response case. For backwards compatibility it still populates `status` in the error case. This inconsistency was missed partially due to a bug in the CLI tests. The assertion on status code was not valid and would always be successful. Thus this also fixes the assertions and tests.	3 years ago
Timothy Messier	99a8875d3e	feat(version): Determine binary version during initalization ... This ensures that checks for features should work, and bails early if that is not the case, since if this fails the binary is essentially broken. This also simplifies code that performs these checks, ie instead of: binaryVersion, err := version.GetReleaseVersion() if err != nil { // handle error? panic? } if version.SupportsFeature(binaryVersion, version.FeatureA) { // code for FeatureA } else { // without FeatureA } Implementations can do: if version.SupportsFeature(version.Binary, version.FeatureA) { // code for FeatureA } else { // without FeatureA }	3 years ago
Todd	7c2d0692f6	Fix NPE and GetReleaseVersion now includes metadata. (#2657)	3 years ago
Irena Rindos	6315821c9a	Add feature manager (#2633) ... * add feature manager	3 years ago