Skip to content

Deprecation plan for legacy parameters #7452

Closed
@bpmct

Description

@bpmct

While we've communicated via docs that we plan on deprecating legacy parameters by the end of April, not all of our users read our docs or changelog.

While we're communicating this to our customers and prospects, let's add a 2-week buffer window while we add a banner on workspaces and templates

This template uses legacy parameters which will be deprecated in the next Coder release. Learn how to migrate in our documentation

Of course, we will add this to our changelog when we deprecate too, but this is one additional measure to avoid data loss.


After entirely moving the code, we should still keep some detection logic (perhaps for 6 months) that explains that they are not supported and prevent builds. This would be much better than some random error.

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions