Sanitize Auth0 user_id for Kubernetes labels (export/import job fix) #60
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Bug Fixes
Fixes job creation failures when Auth0 user IDs (containing |) are used as label values.
Root Cause
username was injected directly into metadata.labels, violating Kubernetes label rules.
Fix
Added sanitizeLabelValue() in handlers/sanitize.go
Applied sanitization when creating job labels and selectors
Preserved original username in metadata.annotations["gen3.original-username"]
Updated Dockerfile to build correctly in forks and CI (no .git dependency)
Affected actions
Export (e.g. Pelican/PFB)
Import jobs (same label pipeline)
Testing
Verified job creation and status endpoints with Auth0 user IDs.
Improvements
Dependency updates
Deployment changes