AAP-62657 Implement logic to extract and populate JWT claims from Controller Jobs #16259
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.
AAP-62657
What is being changed?
Adds
populate_claims_for_workload()function toawx/main/tasks/jobs.py:AutomationControllerJobScopefrom
django-ansible-baseAutomationControllerJobScope.CLAIM_*forconsistency with Gateway
strings
jobs, empty strings, and edge cases
Why is this change needed?
This function is the Controller-side implementation for OIDC workload identity claim population.
While the scope is defined in django-ansible-base (AAP-62105) and validated by Gateway
(AAP-62534), Controller needs to provide the actual job metadata.
The function will be called from
RunJob.build_jwt()(to be implemented in AAP-62693) to:How does this change address the issue?
Notes
This function is not yet called - it will be integrated when
RunJob.build_jwt()isimplemented in AAP-62693. The function signature and behavior are complete and tested, ready for
integration.
Related Tickets
this function)
AutomationControllerJobScopein django-ansible-baseISSUE TYPE
COMPONENT NAME