-
Notifications
You must be signed in to change notification settings - Fork 1
Description
Hello,
First off, thanks for your work on this plugin—it’s a valuable contribution and I appreciate the effort you’ve put into it.
I’m evaluating the plugin for AWX to enable GitHub App authentication. I successfully installed the plugin in our AWX web and task containers, and the awx-manage setup_managed_credential_types command logs that it’s adding the “GitHub App Authentication” credential type. I can even create a credential using this type.
However, when I try to use this credential for a project’s Git repository (configured using the standard Source Control credential type), the plugin-based credential doesn’t appear in the selection list. It seems AWX’s SCM logic expects a credential with the typical username/password structure (e.g. “x-access-token” and a token) to construct the Git clone URL. In contrast, the plugin’s credential schema uses fields like app_id, installation_id, and private_key, and returns a GitHub App token.
Could you please provide guidance on how you use this plugin to actually clone GitHub repositories? Specifically:
• Are there additional configuration steps or injectors needed to map the plugin’s output into a standard SCM format?
• Do you modify the metadata or use a particular process so that the plugin returns the token in the expected username/password format (e.g., with a fixed “x-access-token” as username)?
Any clarification or an example of the workflow you use would be greatly appreciated.
Thanks again for your work on this plugin!
Best regards