@pratheekrebala sorry we broke this for you! This was an arbitrary gate on our side but intentional because we plan on forking the UX while users transfer over.

Is there a missing feature in rich parameters that prevents you from moving legacy ones over?

Thanks for the context @kylecarbs!

I don't have any missing features with rich parameters. I do however use variables with sensitive = true to manage template level parameters.

I ran into this issue while I was working on migrating workspaces to rich parameters. I also tried to delete the workspace using --orphan but I get the same error (Rich paramters can't be used together with legacy parameters.)

Is there anyway for me to delete the workspace while the gate is in place? I am also unable to update the template associated with the workspace because of the same error. The message on the CLI is different but on the server side I get the same message as before.

Output from coder template push [template_name] [template_dir]

CLI:

UI:

Hey @pratheekrebala! Could you please update to the latest release and see if you can remove the affected workspace?

Hey @mtojek, I just tried this and was able to delete both templates and workspaces through both the UI & the CLI.

Thank you for patching this so quickly!