Started making use of some of the extended resource functionality
the framework provides, namely ConfigValidators and ModifyPlan.
ConfigValidators let you validate a config
by itself. You can do stuff like prevent conflicting attributes
(dedicated and serverless in this case).
ModifyPlan seems to be intended to handle things like default values,
but I'm using it to prevent users from making certain changes to
clusters. All of the apply-time validation baked into Update now
lives in this method, as well as validation for the scenario in
the commit title.
Updated the framework to v1.1.1 (hooray stability!) to make use of
ConfigValidators. No changes were necessary. The changelog suggests
that they only removed some deprecated code with the 1.0 update.
Started making use of some of the extended resource functionality the framework provides, namely ConfigValidators and ModifyPlan.
ConfigValidators let you validate a config by itself. You can do stuff like prevent conflicting attributes (dedicated and serverless in this case).
ModifyPlan seems to be intended to handle things like default values, but I'm using it to prevent users from making certain changes to clusters. All of the apply-time validation baked into Update now lives in this method, as well as validation for the scenario in the commit title.
Updated the framework to v1.1.1 (hooray stability!) to make use of ConfigValidators. No changes were necessary. The changelog suggests that they only removed some deprecated code with the 1.0 update.
This change is