Which problem is this feature request solving?
When authenticating using Github App credentials, the github source plugin currently supports only reading the key material from a file via the private_key_path configuration directive.
In scenarios like when cloudquery is run in a CI pipeline job, any key material is typically injected via environment variables so currently one needs to have a separate build step where the contents of the environment variable holding secrets are echoed into a file, so that cloudquery can then use it. This works but is cumbersome.
Describe the solution you'd like
I'd like to have a configuration directive private_key that lets me supply the private key as a string, for instance from an environment variable. This would be mutually exclusive with private_key_path to avoid confusion about what key material is being used.
Pull request (optional)
Which problem is this feature request solving?
When authenticating using Github App credentials, the
githubsource plugin currently supports only reading the key material from a file via theprivate_key_pathconfiguration directive.In scenarios like when cloudquery is run in a CI pipeline job, any key material is typically injected via environment variables so currently one needs to have a separate build step where the contents of the environment variable holding secrets are echoed into a file, so that cloudquery can then use it. This works but is cumbersome.
Describe the solution you'd like
I'd like to have a configuration directive
private_keythat lets me supply the private key as a string, for instance from an environment variable. This would be mutually exclusive withprivate_key_pathto avoid confusion about what key material is being used.Pull request (optional)