Adds an additional type constraint go FnCacheGet and FnCacheGetWithTTL
to enforce that all keys are comparable. This should allow the
removal of various compile time hashability checks that are in
place for existing keys of custom types.
* docs: explain awsic plugin install flag
* expand the use system credential sentence
* Update docs/pages/admin-guides/management/guides/aws-iam-identity-center/migrating-identity-center-from-okta-to-teleport.mdx
Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>
---------
Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>
* Clarify the wording in role editor
Use "Teleport resources" and "Kubernetes resources" instead of
"resources" to make them unambiguous.
* Post-rebase test fix
* SPIFFE X.509 issuer override: CRUD
* tctl support for workload_identity_x509_issuer_override
* Define audit log events
* Emit audit log events
* Add comments to point at the e implementation
* audit events fixtures
* Use DisallowUnknown in tctl
* Support additional claims in JWT-SVIDs
* Exclude the `extra_claims` field in Terraform
* Add a maximum nesting depth
* Add comment to clarify behavior of `PrivateClaims`
* Combine declaration with nil check
Co-authored-by: Tiago Silva <tiago.silva@goteleport.com>
---------
Co-authored-by: Tiago Silva <tiago.silva@goteleport.com>
* Add ValidationSuspender component
This component makes it possible to conditionally hide validation errors
in a subset of form fields. It is required by an upcoming PR to the role
editor that satisfies the UX requirement of not showing validation
errors on newly added sections until the next explicit validation is
requested.
Also: add type information to useRule.
* Hide validation errors on newly added sections
Uses ValidationSuspender to hold validation errors from being displayed
on fields that belong to sections added while the validator is
validating. The newly invalid inputs will be marked as invalid only
after another explicit validation call (for example, when the user
attempts to save data).
* Post-merge test fix
This component makes it possible to conditionally hide validation errors
in a subset of form fields. It is required by an upcoming PR to the role
editor that satisfies the UX requirement of not showing validation
errors on newly added sections until the next explicit validation is
requested.
Also: add type information to useRule.
When we originally broke some of the desktop access code out into
a shared windows package to help with MS SQL access we pulled too
much code. This commit just moves code that is only needed in one
package to the package where it is used, and un-exports it.
No functional changes.
* Decrese in line limit for plugin message formating
Also truncate message blocks that still exceed max slack text block length
* Add link to slack docs explaining text block char limit
* Add cdocumentation for `workload-identity-aws-ra` service
* Apply suggestions from code review
Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>
* Adjust name to be full roles anywhere
---------
Co-authored-by: Paul Gottschling <paul.gottschling@goteleport.com>
* Minor improvements to the role editor
- Drop "New" from "Add New Resource Access"
- Add resource kind names to the collapsed admin rule section title
- Rename “Role Metadata” to “Role Information” and remove tooltip
- Add a description for each tab
* review
Now that all backends implement backend.BackendWithItems the
temporary interface is removed and the Items method is included in
backend.Backend. All wrapper implementations, and backend mocks were
updated accordingly.
The backend reporter used to tally prometheus metrics was updated
with new metrics to track streaming requests since reusing the
batch read requests wouldn't make sense for iteration. This means
that once upstream consumers of the backend start switching from
GetRange to Items the batch read metrics will not be the complete
source of truth. The streaming metrics also lack some of the same
observability since chunk sizes and latency of reads cannot be
known at the reporter level. The only way to provide the same
batch metrics that we have today would require each backend
implementation to be responsible for updating the metrics when
performing their internal reads to supply the Items iterator.
* Move `DownloadConnect` to `teleport`
* Move `AuthorizeDeviceWeb` to `e-teleport`
* Import `TextSelectCopy` from `shared`
* Move `ClusterDropdown` to `teleport`
* Move `IAM_ROLE_NAME_REGEX` to `shared`
* Do not import `Latency` type from `teleport`
* Move `StyledDateRange` to `design`
* Move `FileTransferRequests` to `teleport` and refactor the story
* Take initial session size from the canvas instead of the window
* Do not send resize events when canvas has no height
I'm pretty sure the backend side ignored them anyway, but there's no point in sending those events.
* Prepare `TdpClient` to work on a generic transport layer
* Improve alerts rendering
* Remove Web UI-specific components from the shared desktop session component
* Adjust a story to the new shared component
* Remove optional chaining from `client`, it no longer can be `undefined`
* Replace "username@desktop" with "username on desktop"
* Add test for queuing up deep link launch before app is rendered
* Refactor DeepLinksService to a component
* Add VNet deep link handler
* Add new tab icon to Connect deep link in Web UI
Also, fix the icon in the comp warning, it's supposed to be on the right.
* Use separate field instead of redeclaring existing one
* Pass launchDeepLink as prop rather than mocking whole module
* Add text to VNet toggle button
Dan Upton