-
Notifications
You must be signed in to change notification settings - Fork 236
New issue
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
Cloud Functions Resource #512
Comments
Hi @tokatsu-gc, thank you for your resource request. I've added it to the list of resources we're looking into and will let you know when we have more information. |
+1 We have a specific use case for provisioning the cloud-build slack-notifier which uses Cloud Run. At the moment, we have a rather clunky approach that depends on both KCC and TF. Having everything provisioned through KCC would be ideal. PS. The title says Cloud Functions, but the description talks about Cloud Run, so based on the description this sounds like a dup of #378 |
Hi @tgjonestx , thx for your use case! According to links mentioned in the description, I believe @tokatsu-gc was requesting for Cloud Function resources (but not Cloud Run). |
As an ETA, we are slated to deliver this resource by the end of this year. |
Is this feature available in this year or is there a new ETA? |
Hello! Although we are on target for code completion, we will most like release mid-January due to a release freeze for the Holidays. Apologies about the extended delay. |
Hi, |
This is a request to support Cloud Functions.
In order to support Cloud Functions, Config Connector should support the following things
Register functions.
Manage IAM
Cloud Functions is a handy way to handle light weight tasks.
The number of functions for Cloud Functions is increasing.
With Config Connector, customers can manage functions by a declarative way.
The text was updated successfully, but these errors were encountered: