Ben Potter
d04eaf8392
- [x] Mention Orgs is beta and add a link to get feedback - [x] Add docs on new provisioner authentication architecture and deprecate the old one - [x] Add/update docs for IdP sync - [x] Organization Sync - [x] Group Sync - [x] Role Sync - [x] Modify `coder.com` codebase to add `Premium` and `Beta` pill, and allow multiple pills: https://github.com/coder/coder.com/pull/638 - [x] Replace all mentions of "Enterprise" with "Premium" in docs - [x] edit: change it to "Licensing" - [x] Remove the enterprise page and change all links to coder.com/pricing - [x] Merge #14786 - [x] Add redirects for coder.com to redirect the `using-organizations` guide to the new orgs one and /enterprise to /premium https://github.com/coder/coder.com/pull/645 - [x] Custom roles - [x] https://github.com/coder/coder/pull/14786 - [x] Remove all mentions of orgs experiment - [x] Update in-product copy & links to link to the new docs pages Anything I am missing? --- [Preview this](https://coder.com/docs/@orgs-licenses/admin/organizations) --------- Co-authored-by: Edward Angert <EdwardAngert@users.noreply.github.com> Co-authored-by: EdwardAngert <17991901+EdwardAngert@users.noreply.github.com> Co-authored-by: Jaayden Halko <jaayden.halko@gmail.com>
2.1 KiB
Feature stages
Some Coder features are released in feature stages before they are generally available.
If you encounter an issue with any Coder feature, please submit a GitHub issues or join the Coder Discord.
Early access features
Early access features are neither feature-complete nor stable. We do not recommend using early access features in production deployments.
Coder releases early access features behind an “unsafe” experiment, where they’re accessible but not easy to find.
Experimental features
These features are disabled by default, and not recommended for use in production as they may cause performance or stability issues. In most cases, experimental features are complete, but require further internal testing and will stay in the experimental stage for one month.
Coder may make significant changes to experiments or revert features to a feature flag at any time.
If you plan to activate an experimental feature, we suggest that you use a staging deployment.
You can opt-out of an experiment after you've enabled it.
# Enable all experimental features
coder server --experiments=*
# Enable multiple experimental features
coder server --experiments=feature1,feature2
# Alternatively, use the `CODER_EXPERIMENTS` environment variable.
Available experimental features
| Feature | Description | Available in |
|---|---|---|
notifications |
Sends notifications via SMTP and webhooks following certain events. | mainline, stable |
Beta
Beta features are open to the public, but are tagged with a Beta label.
They’re subject to minor changes and may contain bugs, but are generally ready for use.
General Availability (GA)
All other features have been tested, are stable, and are enabled by default.