Thanks for looking into this, one of the impacts of the scriptlets approach in this case is that the configuration validation code would be somewhat separate from the charm code. If it was a hook on the charm it could be tested along with the rest of the charm code where unit tests would probably do the heavy lifting of the validation.
It would also mean that developers of charms would now also have to learn how to write and test scriptlets which would put another barrier to entry for charm developers.
Thanks for looking into this, one of the impacts of the scriptlets approach in this case is that the configuration validation code would be somewhat separate from the charm code. If it was a hook on the charm it could be tested along with the rest of the charm code where unit tests would probably do the heavy lifting of the validation.
It would also mean that developers of charms would now also have to learn how to write and test scriptlets which would put another barrier to entry for charm developers.