Their is a use case where CI Repos Differ from CD Repos, and the teams would like the generated GH Token from PAC to allow control over these secondary repos, even if they were not the one triggering the pipeline.

1. Both Repos would be assigned to the same Kuberentes Namespace.
2. Some sort of method for allowing the added scope to the repos.

What is the business impact? Please also provide timeframe information.
N/A