Skip to content

Conversation

@raaizik
Copy link
Member

@raaizik raaizik commented Jan 14, 2026

Implement detection of S3 profile changes and automatic data re-upload when S3 data becomes unavailable.
By checking directly the S3 path's contents, the system now detects when expected PV/PVC or VGR/VGRC data is missing from S3 stores. When S3 data is absent, the system triggers automatic re-upload regardless of the ClusterDataProtected condition state, ensuring data consistency when S3 profiles are reconfigured or storage is reset.

Changes

  • Implement S3 path contents checking in isPVAndPVCDataInS3 and isVGRAndVGRCDataInS3
  • Detect when S3 profile changes by checking for missing data in stores
  • Trigger re-upload when S3 data is missing, bypassing ClusterDataProtected checks
  • Extract common S3 data checking logic into generic helper functions
  • Add comprehensive unit tests for PV/PVC and VGR/VGRC profile change detection
  • Reduce code duplication and cognitive complexity

- Implement S3 path contents checking in isPVAndPVCDataInS3 and isVGRAndVGRCDataInS3
- Detect when S3 profile changes by checking for missing data in stores
- Trigger re-upload when S3 data is missing, bypassing ClusterDataProtected checks
- Extract common S3 data checking logic into generic helper functions
- Add comprehensive unit tests for PV/PVC and VGR/VGRC profile change detection
- Fix all linting errors: blank lines before returns, error handling in tests
- Reduce code duplication and cognitive complexity

Signed-off-by: raaizik <132667934+raaizik@users.noreply.github.com>
@raaizik raaizik force-pushed the handle-s3-profile-changes branch from 0cb45f8 to dd1811b Compare January 15, 2026 11:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant