We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I was wondering if this project is meant to reach a stable state or if it is a proof of concept.
I see some lines of code that seem unfinished: https://github.com/aws-ia/cloudformation-pagerduty-resource-providers/blob/main/PagerDuty-Services-Integration/src/handlers.ts#L73 https://github.com/aws-ia/cloudformation-pagerduty-resource-providers/blob/main/PagerDuty-Services-Integration/pagerduty-services-integration.json#L316 https://github.com/aws-ia/cloudformation-pagerduty-resource-providers/blob/main/PagerDuty-Services-Integration/src/handlers.ts#L99
Also, the integration key is not exposed, so downstream resources cannot reference it.
I would love to know if this is something I can plan within the near future.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I was wondering if this project is meant to reach a stable state or if it is a proof of concept.
I see some lines of code that seem unfinished:
https://github.com/aws-ia/cloudformation-pagerduty-resource-providers/blob/main/PagerDuty-Services-Integration/src/handlers.ts#L73
https://github.com/aws-ia/cloudformation-pagerduty-resource-providers/blob/main/PagerDuty-Services-Integration/pagerduty-services-integration.json#L316
https://github.com/aws-ia/cloudformation-pagerduty-resource-providers/blob/main/PagerDuty-Services-Integration/src/handlers.ts#L99
Also, the integration key is not exposed, so downstream resources cannot reference it.
I would love to know if this is something I can plan within the near future.
The text was updated successfully, but these errors were encountered: