There are already Custom Resources in the public CloudFormation Registry cloudformation-github-resource-providers and cdk-cloudformation.
My understanding is they are complementary to our library. They are really good for regular use cases and can be used complementary with this custom construct.
This more flexible custom construct fills then the gap what is not implemented and also the ability to use a Github app or unauthenticated instead a PAT.
We may skip on higher constructs and refer to such libraries. Additional we can give some quickstart hint and an example for interop.
thx Konstantin
My understanding is they are complementary to our library. They are really good for regular use cases and can be used complementary with this custom construct.
This more flexible custom construct fills then the gap what is not implemented and also the ability to use a Github app or unauthenticated instead a PAT.
We may skip on higher constructs and refer to such libraries. Additional we can give some quickstart hint and an example for interop.
thx Konstantin