Deployment documentation #64
Conversation
docs/deployment.md
Outdated
|
|
||
| ## Deploying locally | ||
|
|
||
| Your function can run locally either by starting it through Visual |
There was a problem hiding this comment.
If it depends on the Invoker or a custom invoker, seems evident to us but might not be to everyone.
docs/deployment.md
Outdated
| - [Codelab for C#](https://codelabs.developers.google.com/codelabs/cloud-run-hello-csharp/index.html) | ||
|
|
||
| The instructions apply to functions in exactly the same way as | ||
| normal, with the same Dockerfile configuration. The `PORT` |
There was a problem hiding this comment.
This sentence is weird: in exactly the same way as a normal, ?
There was a problem hiding this comment.
Fixed - but check that it's clear :)
| ## Deploying to Google Cloud Functions | ||
|
|
||
| > **NOTE:** | ||
| > The `dotnet3` runtime is currently available on an "allow |
There was a problem hiding this comment.
If there are instructions on how to get whitelisted, or at least a note on who gets whitelisted, we can avoid people asking.
| The command line options are used to specify how the function is | ||
| triggered. | ||
|
|
||
| ### HTTP functions |
There was a problem hiding this comment.
No section for Cloud Events?
There was a problem hiding this comment.
Renamed "legacy event" to "Cloud Event" now that that's all we have.
|
A couple of my comments here had already been replied to in the bigger PR so ignore here. |
| ## Deploying to Google Cloud Functions | ||
|
|
||
| > **NOTE:** | ||
| > The `dotnet3` runtime is currently available on an "allow |
docs/deployment.md
Outdated
| ------------------------ | -------------- | -------------------------- | ||
| Cloud Storage operation | StorageObject | --trigger-event google.storage.object.finalize --trigger-resource ***my-gcs-bucket*** | ||
| Pub/Sub message | PubSubMessage | --trigger-topic ***my-pubsub-topic-id*** | ||
| Firestore event | FirestoreEvent | --trigger event providers/cloud.firestore/eventTypes/document.write --trigger-resource 'projects/***my-project***/databases/(default)/documents/***my-collection***/{document}' |
There was a problem hiding this comment.
Is there a dash missing? --trigger event .
There was a problem hiding this comment.
Well spotted - fixed, thanks.
docs/deployment.md
Outdated
|
|
||
| ## Deploying locally | ||
|
|
||
| Your function can run locally either by starting it through Visual |
docs/deployment.md
Outdated
| - [Codelab for C#](https://codelabs.developers.google.com/codelabs/cloud-run-hello-csharp/index.html) | ||
|
|
||
| The instructions apply to functions in exactly the same way as | ||
| normal, with the same Dockerfile configuration. The `PORT` |
There was a problem hiding this comment.
Fixed - but check that it's clear :)
| ## Deploying to Google Cloud Functions | ||
|
|
||
| > **NOTE:** | ||
| > The `dotnet3` runtime is currently available on an "allow |
| The command line options are used to specify how the function is | ||
| triggered. | ||
|
|
||
| ### HTTP functions |
There was a problem hiding this comment.
Renamed "legacy event" to "Cloud Event" now that that's all we have.
docs/deployment.md
Outdated
| ------------------------ | -------------- | -------------------------- | ||
| Cloud Storage operation | StorageObject | --trigger-event google.storage.object.finalize --trigger-resource ***my-gcs-bucket*** | ||
| Pub/Sub message | PubSubMessage | --trigger-topic ***my-pubsub-topic-id*** | ||
| Firestore event | FirestoreEvent | --trigger event providers/cloud.firestore/eventTypes/document.write --trigger-resource 'projects/***my-project***/databases/(default)/documents/***my-collection***/{document}' |
There was a problem hiding this comment.
Well spotted - fixed, thanks.
No description provided.