Pydantypes – The missing Pydantic types for cloud, DevOps, AI

Name: Pydantypes – The missing Pydantic types for cloud, DevOps, AI
Availability: InStock
Author: theroot_

by theroot_·Mar 1, 2026·2 points·0 comments

Visit Project View on HN

AI Analysis

●●●BangerSolve My ProblemSlick

100+ validated types for cloud infra—S3Uri.bucket, IamRoleArn.role_name built-in.

Strengths

•Decomposes instead of just validates (S3Uri gives .bucket and .key properties, not just pass/fail)
•LabelEnum with deprecation/alias resolution solves real production label-evolution pain
•1k+ tests, full type hints, covers AWS/Azure/GCP/DevOps/data/AI domains comprehensively

Weaknesses

•Solves a real problem but is fundamentally a validation library in a crowded Pydantic ecosystem
•No clear moat over hand-rolled regex validators or pydantic-extra-types

Post Description

I’ve spent the last few years building infra across AWS, Azure, K8s, and ML pipelines.

Every project had the same problem: cloud identifiers like S3 URIs, IAM ARNs, Docker refs, and Azure resource IDs living as bare strings with hand-rolled validation.

pydantypes gives you Pydantic v2 types that validate and decompose these into structured attributes. S3Uri gives you .bucket and .key, DockerImageRef gives you .registry, .tag, .digest, etc.

Covers AWS, Azure, GCP, DevOps, web identifiers, and data engineering.

There’s also LabelEnum for AI/ML classification labels with built-in deprecation, retirement, and alias resolution.

If you’ve ever had to evolve a label taxonomy in production, that one might be worth a look on its own.

Complements pydantic-extra-types. 1k+ tests, fully typed, MIT. Happy to take suggestions for types to add.