Skip to content

feat: Disable auto-enroll via environment variable#47679

Merged
codingllama merged 1 commit intomasterfrom
codingllama/autoenroll-offswitch
Oct 18, 2024
Merged

feat: Disable auto-enroll via environment variable#47679
codingllama merged 1 commit intomasterfrom
codingllama/autoenroll-offswitch

Conversation

@codingllama
Copy link
Copy Markdown
Contributor

Users or remote admins can now set TELEPORT_DEVICE_AUTO_ENROLL_DISABLED=1 to disable auto-enroll in their machine, regardless of cluster setting.

Changelog: Auto-enroll may be locally disabled using the TELEPORT_DEVICE_AUTO_ENROLL_DISABLED=1 environment variable

@codingllama
Copy link
Copy Markdown
Contributor Author

This one is a bit experimental, but I think it could help if a customer wants to automatically exclude a certain category of machines from auto-enroll.

@rosstimothy
Copy link
Copy Markdown
Contributor

This one is a bit experimental

For these kinds of things we've been using TELEPORT_UNSTABLE_FOO

@codingllama
Copy link
Copy Markdown
Contributor Author

codingllama commented Oct 17, 2024

This one is a bit experimental

For these kinds of things we've been using TELEPORT_UNSTABLE_FOO

It's not experimental in that sense, it was more in that I was still looking for confirmation on whether it would be useful. The answer is "yes" so I think the proposed env var is better.

@rosstimothy
Copy link
Copy Markdown
Contributor

One of the other reasons the TELEPORT_UNSTABLE prefix has been used is to prevent people from relying on the environment variables longterm. Is this going to be a thing in perpetuity or do you plan on removing this in favor of another mechanism in the future? If the latter I think the TELEPORT_UNSTABLE prefix should be used here.

@codingllama
Copy link
Copy Markdown
Contributor Author

codingllama commented Oct 18, 2024

One of the other reasons the TELEPORT_UNSTABLE prefix has been used is to prevent people from relying on the environment variables longterm. Is this going to be a thing in perpetuity or do you plan on removing this in favor of another mechanism in the future? If the latter I think the TELEPORT_UNSTABLE prefix should be used here.

No plans to remove it, seems like an useful toggle to have. The cost is just a handful of lines of relatively straightforward production code.

Copy link
Copy Markdown
Contributor

@rosstimothy rosstimothy left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the addition context @codingllama. I just wanted to ensure we were being consistent with environment variable naming.

@codingllama codingllama force-pushed the codingllama/autoenroll-offswitch branch from 1fa2a9b to 5bae9f9 Compare October 18, 2024 14:37
@codingllama
Copy link
Copy Markdown
Contributor Author

Conflicts solved, no code changes. PTAL @rudream @ryanclark.

@public-teleport-github-review-bot public-teleport-github-review-bot Bot removed the request for review from rudream October 18, 2024 14:52
@codingllama codingllama added this pull request to the merge queue Oct 18, 2024
Merged via the queue into master with commit 6669f2d Oct 18, 2024
@codingllama codingllama deleted the codingllama/autoenroll-offswitch branch October 18, 2024 17:20
@public-teleport-github-review-bot
Copy link
Copy Markdown

@codingllama See the table below for backport results.

Branch Result
branch/v14 Create PR
branch/v15 Create PR
branch/v16 Create PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants