Skip to content

Conversation

@BackendBits
Copy link
Collaborator

  • feat: Support for Registry V2

  • fix: import issue fixed

  • fix: formatting issue

  • fix: formatting issue 2

Pull Request

Summary

Added RegDef V2 schema support with automatic version detection and authConfig validation for public cloud registries (AWS, Azure, GCP), maintaining full backward compatibility with V1 RegDefs.

Issue

Enables validation of RegDef V2 files for public cloud registry support with enhanced authentication mechanisms.

Breaking Change?

  • Yes
  • No

Scope / Project

qubership-envgene - RegDef validation

Implementation Notes

Enhanced validation in validate_appregdefs():

  • Auto-detects RegDef version from YAML content (defaults to V1 if not specified)
  • Routes to appropriate schema: regdef.schema.json (V1) or regdef-v2.schema.json (V2)

Added validate_regdef_v2_authconfig():

  • Validates authConfig references in artifact configs
  • Ensures referenced authConfigs exist with clear error messages

New RegDef V2 Schema:

  • Supports cloud provider authentication (AWS, Azure, GCP)
  • Per-artifact-type authConfig references and repository domains

Tests / Evidence

  • V1 and V2 files validate against correct schemas
  • AuthConfig reference validation working
  • Console output shows schema selection per file

Additional Notes

Files Modified: scripts/build_env/main.py, schemas/regdef-v2.schema.json (new)

Migration: V1 RegDefs work unchanged. V2 detected by version: "2.0" field.

@BackendBits BackendBits force-pushed the feature/support_registry_v2 branch from b94b0be to fa5b13c Compare October 27, 2025 11:01
@github-actions github-actions bot added the bug Something isn't working label Oct 27, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants