- Notifications
You must be signed in to change notification settings - Fork1k
docs: remove unsupported legacy parameters#7799
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Uh oh!
There was an error while loading.Please reload this page.
Co-authored-by: Muhammad Atif Ali <atif@coder.com>
| >⚠️ Migration is available until v0.24.0 (Jun 2023) release. | ||
| Terraform variables shouldn't be used for workspace scoped parameters anymore, and it's recommended to convert variables to`coder_parameter` resources. To make the migration smoother, there is a special property introduced - | ||
| `legacy_variable` and`legacy_variable_name` , which can link`coder_parameter` with a legacy variable. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
Also willlegacy_variable andlegacy_variable_name still be usable in v0.24.0?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others.Learn more.
In v0.24.0 they might be not really useful, but it should be fine to keep them for a while. We can also mark them as deprecated in the provider schema. Good catch, Atif 👍 I will check this next week.
Related:#7663
This PR adds a short paragraph describing admin actions to fix/delete unsupported workspaces if they weren't migrated in time.