Azure-docs: This is not about Cosmos DB triggers.

[alekseys]

The term "Cosmos DB trigger" here is misused. Trigger has a special meaning in Cosmos DB and has nothing to do with Azure Functions. Suggest to use Function trigger or something else instead.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: da525782-702a-0c0b-0ced-32b124c527a3
• Version Independent ID: 97757a1f-9919-d6c8-868e-776018bb8f9a
• Content: Serverless database computing - Azure Functions and Azure Cosmos DB
• Content Source: articles/cosmos-db/serverless-computing-database.md
• Service: cosmos-db
• GitHub Login: @SnehaGunda
• Microsoft Alias: sngun

[KrishnaG-MSFT]

@alekseys Thanks for your comment. We are actively investigating and will get back to you shortly.

[KalyanChanumolu-MSFT]

@alekseys Thank you for the feedback. This is being assigned to the content author to evaluate and update as appropriate. 

@SnehaGunda We have heard similar feedback on other forums as well.
The terminology is being confused with Pre and Post triggers.

[SnehaGunda]

@alekseys Thanks for pointing out the issue, should we use "Azure Functions trigger for Cosmos DB" instead?

@ealsur FYI regarding the feedback on terminology, please confirm if the above term is correct instead? I can scrub all the docs with this term. Also, please consider the new version for any future doc updates you make.

[ealsur]

Name follows Azure Functions naming, where the service name is a prefix to the type of integration, like Event Hub Trigger, or Azure Signal R Output Binding, so the text in our articles should follow that.

The body of the articles mention Azure Functions, and the TOC is within Change Feed, not within programmability.

The title can be changed as you see fit, but the term "Cosmos DB Trigger" in the context of Azure Functions in the body shouldn't be changed unless signed off first in the Azure Functions docs.

---

From: Sneha Gunda [e-mail]
Sent: Tuesday, July 16, 2019 7:38:40 PM
To: MicrosoftDocs/azure-docs
Cc: Matias Quaranta; Mention
Subject: Re: [MicrosoftDocs/azure-docs] This is not about Cosmos DB triggers. (#34886)

@alekseyshttps://github.com/alekseys Thanks for pointing out the issue, should we use "Azure Functions trigger for Cosmos DB" instead?

@ealsurhttps://github.com/ealsur FYI regarding the feedback on terminology, please confirm if the above term is correct instead? I can scrub all the docs with this term. Also, please consider the new version for any future doc updates you make.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/azure-docs/issues/34886?email_source=notifications&email_token=AAMOY6O76QQ4IWOHGJHAPMLP72A3BA5CNFSM4IAB7AG2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD2C26ZA#issuecomment-512077668, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AAMOY6JN2QZ7GNAITZUKCYTP72A3BANCNFSM4IAB7AGQ.

[SnehaGunda]

@alekseys I made some terminology changes to few docs in the above PR. I will have a chat with @ealsur after he is back from vacation to check if we need to revert anything. I see that the Azure functions docs use the terms Cosmos DB trigger, EventHubs trigger.... however I don't know technically if this is the right term. We may have to discuss with the Functions team, I will work with Matias after he is back.

We will close this issue for now.

please-close