Initially we planned to extend validation in both the browser & CLI UIs

I don't remember now if CLI supports validation of monotonicity. As long as it usescodersdk.ValidateWorkspaceBuildParameters, it should be supported. Maybe drop another CLI test to verify the behavior?

The CLI doesn't seem to have any client-side validation for options that I can see. Thesurvey lib which powers the options selector exposes aWithValidator hook which we could implement?

, but we agreed to defer this until#7099 is implemented which would centralise all the logic.

Since validation might work well on the CLI, I'm wondering if it isn't a low hanging fruit to come up with a temporary fix for the frontend. I'm unsure how frontend deals with monotonicity right now.

Frontend validation can work but it's not possible to display the error inline with theRadioGroup component according to@BrunoQuaresma.

The CLI doesn't seem to have any client-side validation for options that I can see. The survey lib which powers the options selector exposes a WithValidator hook which we could implement?

AFAIR There were some problems with testingselect input assurvey always picked the first item on the list, hence no tests were implemented.

Anyway, if CLI and UI depend on backend validation here, then user will be warned about value conflict. If you want to try, you can modifycli/update_test.go to address themonotonicity use case, but I'm also cool if it is hard/impossible to do 👍

cli/update_test.go

Will do, thanks!

cli/update_test.go

Will do, thanks!

@mtojek I added a test inaae5463, PTAL?

I also updated the provider now thatcoder/terraform-provider-coder#202 is merged.