[Pydantic v2] Update server and compute config to use pydantic v2 #978
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR is starting the process of moving to pydantic v2.
This first step is migrating the code for server and compute manager configuration to use the pydantic v2 models. These are isolated uses and don't affect any other models, and should be simple and safe.
As a benefit, errors related to compute manager configuration should be much easier to read due to the discriminated union functionality now available.
This does sneak in a few small changes to the configuration:
queue_tagsis now removed from the compute manager configuration. Usecompute_tagsinstead.strict_queue_tagsis deprecated, but still usable for now. Replace withstrict_compute_tagsStatus