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
ERROR: creating resources of type "windows_desktop" is not supported #27106
Comments
We should probably support |
The concern here is mostly about having a dynamic way to insert hosts and set labels on them without requiring the use of the |
To date: we have supported registering desktops in a few ways: 1. By discovering them from LDAP 2. By listing "static hosts" in the configuration file 3. Via our API https://github.com/gravitational/teleport/tree/master/examples/desktop-registration This extends tctl to support creating a desktop from a YAML resource definition, which provides an alternative for those who want more control over the name and labels of their desktops, but don't want to write and maintain an integration using our API. Note: this also makes it possible to `tctl edit` an existing desktop, but we do not recommend doing so if the desktop was created via methods 1 or 2 above, as any changes will be overwritten on the next heartbeat. Closes #27106
To date: we have supported registering desktops in a few ways: 1. By discovering them from LDAP 2. By listing "static hosts" in the configuration file 3. Via our API https://github.com/gravitational/teleport/tree/master/examples/desktop-registration This extends tctl to support creating a desktop from a YAML resource definition, which provides an alternative for those who want more control over the name and labels of their desktops, but don't want to write and maintain an integration using our API. Note: this also makes it possible to `tctl edit` an existing desktop, but we do not recommend doing so if the desktop was created via methods 1 or 2 above, as any changes will be overwritten on the next heartbeat. Closes #27106
To date: we have supported registering desktops in a few ways: 1. By discovering them from LDAP 2. By listing "static hosts" in the configuration file 3. Via our API https://github.com/gravitational/teleport/tree/master/examples/desktop-registration This extends tctl to support creating a desktop from a YAML resource definition, which provides an alternative for those who want more control over the name and labels of their desktops, but don't want to write and maintain an integration using our API. Closes #27106
To date: we have supported registering desktops in a few ways: 1. By discovering them from LDAP 2. By listing "static hosts" in the configuration file 3. Via our API https://github.com/gravitational/teleport/tree/master/examples/desktop-registration This extends tctl to support creating a desktop from a YAML resource definition, which provides an alternative for those who want more control over the name and labels of their desktops, but don't want to write and maintain an integration using our API. Note: this also makes it possible to `tctl edit` an existing desktop, but we do not recommend doing so if the desktop was created via methods 1 or 2 above, as any changes will be overwritten on the next heartbeat. Closes #27106
To date: we have supported registering desktops in a few ways: 1. By discovering them from LDAP 2. By listing "static hosts" in the configuration file 3. Via our API https://github.com/gravitational/teleport/tree/master/examples/desktop-registration This extends tctl to support creating a desktop from a YAML resource definition, which provides an alternative for those who want more control over the name and labels of their desktops, but don't want to write and maintain an integration using our API. Closes #27106
Expected behavior:
tctl edit windows_desktop/<uuid>
(ortctl create -f windows_desktop.yaml
) should work to edit entries added vianon_ad_hosts
.Commands like
tctl update windows_desktop/<uuid> --set-labels=environment=test
would also be useful to avoid inline editing.Essentially a better supported method to set labels on Windows hosts would be useful.
Current behavior:
Bug details:
The text was updated successfully, but these errors were encountered: