Skip to content

Commit cab4d67

Browse files
hallvictoriahallvictoria
committed
Fix scorecard
1 parent 10c3aff commit cab4d67

5 files changed

+35
-35
lines changed

‎articles/azure-functions/functions-bindings-cosmosdb-v2-input.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -246,7 +246,7 @@ The following example shows a [C# function](functions-dotnet-class-library.md) t
246246
The example shows how to use a binding expression in the `SqlQuery` parameter. You can pass route data to the `SqlQuery` parameter as shown, but currently [you can't pass query string values](https://github.com/Azure/azure-functions-host/issues/2554#issuecomment-392084583).
247247

248248
> [!NOTE]
249-
> If you need to query by just the ID, it is recommended to use a look up, like the [previous examples](#http-trigger-look-up-id-from-query-string-c), as it will consume less [request units](/azure/cosmos-db/request-units). Point read operations (GET) are [more efficient](/azure/cosmos-db/optimize-cost-reads-writes) than queries by ID.
249+
> If you need to query by just the ID, it is recommended to use a lookup, like the [previous examples](#http-trigger-look-up-id-from-query-string-c), as it consumes less [request units](/azure/cosmos-db/request-units). Point read operations (GET) are [more efficient](/azure/cosmos-db/optimize-cost-reads-writes) than queries by ID.
250250
>
251251
252252
```cs
@@ -635,7 +635,7 @@ public class DocByIdFromRoute {
635635
The following example shows a Java function that retrieves a single document. The function is triggered by an HTTP request that uses a route parameter to specify the ID to look up. That ID is used to retrieve a document from the specified database and collection, converting the result set to a `ToDoItem[]`, since many documents may be returned, depending on the query criteria.
636636

637637
> [!NOTE]
638-
> If you need to query by just the ID, it is recommended to use a look up, like the [previous examples](#http-trigger-look-up-id-from-query-string---pojo-parameter-java), as it will consume less [request units](/azure/cosmos-db/request-units). Point read operations (GET) are [more efficient](/azure/cosmos-db/optimize-cost-reads-writes) than queries by ID.
638+
> If you need to query by just the ID, it is recommended to use a lookup, like the [previous examples](#http-trigger-look-up-id-from-query-string---pojo-parameter-java), as it consumes less [request units](/azure/cosmos-db/request-units). Point read operations (GET) are [more efficient](/azure/cosmos-db/optimize-cost-reads-writes) than queries by ID.
639639
>
640640
641641
```java
@@ -1260,8 +1260,8 @@ This section contains the following examples that read a single document by spec
12601260

12611261
The examples depend on whether you use the [v1 or v2 Python programming model](functions-reference-python.md).
12621262

1263-
### Using SDK-Type Bindings for CosmosDB (Preview)
1264-
This example uses SDK types to directly access the underlying [`CosmosClient`](https://github.com/Azure/azure-functions-python-extensions/blob/dev/azurefunctions-extensions-bindings-cosmosdb/samples/cosmosdb_samples_cosmosclient/function_app.py) object provided by the CosmosDB input binding:
1263+
### Using SDK-Type Bindings for Cosmos DB (Preview)
1264+
This example uses SDK types to directly access the underlying [`CosmosClient`](https://github.com/Azure/azure-functions-python-extensions/blob/dev/azurefunctions-extensions-bindings-cosmosdb/samples/cosmosdb_samples_cosmosclient/function_app.py) object provided by the Cosmos DB input binding:
12651265

12661266
The function loops through all the databases and logs their IDs.
12671267
```python
@@ -1710,7 +1710,7 @@ Updates to documents are not made automatically upon function exit. To update do
17101710
::: zone-end
17111711
::: zone pivot="programming-language-python"
17121712
Data is made available to the function via a `DocumentList` parameter. Changes made to the document are not automatically persisted.
1713-
Functions also supports Python SDK type bindings for Azure Cosmos, which lets you work with data using these underlying SDK types:
1713+
Functions also support Python SDK type bindings for Azure Cosmos, which lets you work with data using these underlying SDK types:
17141714

17151715
+ [`ContainerProxy`](https://github.com/Azure/azure-functions-python-extensions/blob/dev/azurefunctions-extensions-bindings-cosmosdb/samples/cosmosdb_samples_containerproxy/function_app.py)
17161716
+ [`CosmosClient`](https://github.com/Azure/azure-functions-python-extensions/blob/dev/azurefunctions-extensions-bindings-cosmosdb/samples/cosmosdb_samples_cosmosclient/function_app.py)

‎articles/azure-functions/functions-bindings-service-bus-trigger.md

Lines changed: 14 additions & 14 deletions
Original file line numberDiff line numberDiff line change
@@ -394,15 +394,15 @@ Both [in-process](functions-dotnet-class-library.md) and [isolated worker proces
394394

395395
The following table explains the properties you can set using this trigger attribute:
396396

397-
| Property |Description|
398-
| --- | --- |
399-
|**QueueName**|Name of the queue to monitor. Set only if monitoring a queue, not for a topic. |
400-
|**TopicName**|Name of the topic to monitor. Set only if monitoring a topic, not for a queue.|
401-
|**SubscriptionName**|Name of the subscription to monitor. Set only if monitoring a topic, not for a queue.|
402-
|**Connection**| The name of an app setting or setting collection that specifies how to connect to Service Bus. See [Connections](#connections).|
403-
|**IsBatched**| Messages are delivered in batches. Requires an array or collection type. |
404-
|**IsSessionsEnabled**|`true` if connecting to a [session-aware](../service-bus-messaging/message-sessions.md) queue or subscription. `false` otherwise, which is the default value.|
405-
|**AutoCompleteMessages**| `true` if the trigger should automatically complete the message after a successful invocation. `false` if it should not, such as when you are [handling message settlement in code](#usage). If not explicitly set, the behavior will be based on the [`autoCompleteMessages` configuration in `host.json`][host-json-autoComplete].|
397+
| Property | Description |
398+
| --- |---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------|
399+
|**QueueName**| Name of the queue to monitor. Set only if monitoring a queue, not for a topic. |
400+
|**TopicName**| Name of the topic to monitor. Set only if monitoring a topic, not for a queue. |
401+
|**SubscriptionName**| Name of the subscription to monitor. Set only if monitoring a topic, not for a queue. |
402+
|**Connection**| The name of an app setting or setting collection that specifies how to connect to Service Bus. See [Connections](#connections). |
403+
|**IsBatched**| Messages are delivered in batches. Requires an array or collection type. |
404+
|**IsSessionsEnabled**| `true` if connecting to a [session-aware](../service-bus-messaging/message-sessions.md) queue or subscription. `false` otherwise, which is the default value. |
405+
|**AutoCompleteMessages**| `true` if the trigger should automatically complete the message after a successful invocation. `false` if it should not, such as when you are [handling message settlement in code](#usage). If not explicitly set, the behavior is based on the [`autoCompleteMessages` configuration in `host.json`][host-json-autoComplete]. |
406406

407407
# [In-process model](#tab/in-process)
408408

@@ -417,7 +417,7 @@ The following table explains the properties you can set using this trigger attri
417417
|**Access**|Access rights for the connection string. Available values are `manage` and `listen`. The default is `manage`, which indicates that the `connection` has the **Manage** permission. If you use a connection string that does not have the **Manage** permission, set `accessRights` to "listen". Otherwise, the Functions runtime might fail trying to do operations that require manage rights. In Azure Functions version 2.x and higher, this property is not available because the latest version of the Service Bus SDK doesn't support manage operations.|
418418
|**IsBatched**| Messages are delivered in batches. Requires an array or collection type. |
419419
|**IsSessionsEnabled**|`true` if connecting to a [session-aware](../service-bus-messaging/message-sessions.md) queue or subscription. `false` otherwise, which is the default value.|
420-
|**AutoComplete**|`true` Whether the trigger should automatically call complete after processing, or if the function code will manually call complete.<br/><br/>If set to `true`, the trigger completes the message automatically if the function execution completes successfully, and abandons the message otherwise.<br/><br/>When set to `false`, you are responsible for calling [ServiceBusReceiver](/dotnet/api/azure.messaging.servicebus.servicebusreceiver) methods to complete, abandon, or deadletter the message, session, or batch. When an exception is thrown (and none of the `ServiceBusReceiver` methods are called), then the lock remains. Once the lock expires, the message is re-queued with the `DeliveryCount` incremented and the lock is automatically renewed. |
420+
|**AutoComplete**|`true` Whether the trigger should automatically call complete after processing, or if the function code will manually call complete.<br/><br/>If set to `true`, the trigger completes the message automatically if the function execution completes successfully, and abandons the message otherwise.<br/><br/>When set to `false`, you are responsible for calling [ServiceBusReceiver](/dotnet/api/azure.messaging.servicebus.servicebusreceiver) methods to complete, abandon, or deadletter the message, session, or batch. When an exception is thrown (and none of the `ServiceBusReceiver` methods are called), then the lock remains. Once the lock expires, the message is requeued with the `DeliveryCount` incremented and the lock is automatically renewed. |
421421

422422
---
423423
[!INCLUDE [app settings to local.settings.json](../../includes/functions-app-settings-local.md)]
@@ -481,7 +481,7 @@ The following table explains the properties that you can set on the `options` ob
481481
|**connection**| The name of an app setting or setting collection that specifies how to connect to Service Bus. See [Connections](#connections).|
482482
|**accessRights**| Access rights for the connection string. Available values are `manage` and `listen`. The default is `manage`, which indicates that the `connection` has the **Manage** permission. If you use a connection string that does not have the **Manage** permission, set `accessRights` to "listen". Otherwise, the Functions runtime might fail trying to do operations that require manage rights. In Azure Functions version 2.x and higher, this property is not available because the latest version of the Service Bus SDK doesn't support manage operations.|
483483
|**isSessionsEnabled**| `true` if connecting to a [session-aware](../service-bus-messaging/message-sessions.md) queue or subscription. `false` otherwise, which is the default value.|
484-
|**autoComplete**| Must be `true` for non-C# functions, which means that the trigger should either automatically call complete after processing, or the function code manually calls complete.<br/><br/>When set to `true`, the trigger completes the message automatically if the function execution completes successfully, and abandons the message otherwise.<br/><br/>Exceptions in the function results in the runtime calls `abandonAsync` in the background. If no exception occurs, then `completeAsync` is called in the background. This property is available only in Azure Functions 2.x and higher. |
484+
|**autoComplete**| Must be `true` for non-C# functions, which means that the trigger should either automatically call complete after processing, or the function code manually calls complete.<br/><br/>When set to `true`, the trigger completes the message automatically if the function execution completes successfully, and abandons the message otherwise.<br/><br/>Exceptions in the function results in the runtime call `abandonAsync` in the background. If no exception occurs, then `completeAsync` is called in the background. This property is available only in Azure Functions 2.x and higher. |
485485

486486
# [Model v3](#tab/nodejs-v3)
487487

@@ -498,7 +498,7 @@ The following table explains the binding configuration properties that you set i
498498
|**connection**| The name of an app setting or setting collection that specifies how to connect to Service Bus. See [Connections](#connections).|
499499
|**accessRights**| Access rights for the connection string. Available values are `manage` and `listen`. The default is `manage`, which indicates that the `connection` has the **Manage** permission. If you use a connection string that does not have the **Manage** permission, set `accessRights` to "listen". Otherwise, the Functions runtime might fail trying to do operations that require manage rights. In Azure Functions version 2.x and higher, this property is not available because the latest version of the Service Bus SDK doesn't support manage operations.|
500500
|**isSessionsEnabled**| `true` if connecting to a [session-aware](../service-bus-messaging/message-sessions.md) queue or subscription. `false` otherwise, which is the default value.|
501-
|**autoComplete**| Must be `true` for non-C# functions, which means that the trigger should either automatically call complete after processing, or the function code manually calls complete.<br/><br/>When set to `true`, the trigger completes the message automatically if the function execution completes successfully, and abandons the message otherwise.<br/><br/>Exceptions in the function results in the runtime calls `abandonAsync` in the background. If no exception occurs, then `completeAsync` is called in the background. This property is available only in Azure Functions 2.x and higher. |
501+
|**autoComplete**| Must be `true` for non-C# functions, which means that the trigger should either automatically call complete after processing, or the function code manually calls complete.<br/><br/>When set to `true`, the trigger completes the message automatically if the function execution completes successfully, and abandons the message otherwise.<br/><br/>Exceptions in the function results in the runtime call `abandonAsync` in the background. If no exception occurs, then `completeAsync` is called in the background. This property is available only in Azure Functions 2.x and higher. |
502502

503503
---
504504

@@ -520,7 +520,7 @@ The following table explains the binding configuration properties that you set i
520520
|**connection**| The name of an app setting or setting collection that specifies how to connect to Service Bus. See [Connections](#connections).|
521521
|**accessRights**| Access rights for the connection string. Available values are `manage` and `listen`. The default is `manage`, which indicates that the `connection` has the **Manage** permission. If you use a connection string that does not have the **Manage** permission, set `accessRights` to "listen". Otherwise, the Functions runtime might fail trying to do operations that require manage rights. In Azure Functions version 2.x and higher, this property is not available because the latest version of the Service Bus SDK doesn't support manage operations.|
522522
|**isSessionsEnabled**| `true` if connecting to a [session-aware](../service-bus-messaging/message-sessions.md) queue or subscription. `false` otherwise, which is the default value.|
523-
|**autoComplete**| Must be `true` for non-C# functions, which means that the trigger should either automatically call complete after processing, or the function code manually calls complete.<br/><br/>When set to `true`, the trigger completes the message automatically if the function execution completes successfully, and abandons the message otherwise.<br/><br/>Exceptions in the function results in the runtime calls `abandonAsync` in the background. If no exception occurs, then `completeAsync` is called in the background. This property is available only in Azure Functions 2.x and higher. |
523+
|**autoComplete**| Must be `true` for non-C# functions, which means that the trigger should either automatically call complete after processing, or the function code manually calls complete.<br/><br/>When set to `true`, the trigger completes the message automatically if the function execution completes successfully, and abandons the message otherwise.<br/><br/>Exceptions in the function results in the runtime call `abandonAsync` in the background. If no exception occurs, then `completeAsync` is called in the background. This property is available only in Azure Functions 2.x and higher. |
524524

525525
[!INCLUDE [app settings to local.settings.json](../../includes/functions-app-settings-local.md)]
526526

@@ -613,7 +613,7 @@ The Service Bus instance is available via the parameter configured in the *funct
613613
::: zone pivot="programming-language-python"
614614
The queue message is available to the function via a parameter typed as `func.ServiceBusMessage`. The Service Bus message is passed into the function as either a string or JSON object.
615615

616-
Functions also supports Python SDK type bindings for Azure Service Bus, which lets you work with data using these underlying SDK types:
616+
Functions also support Python SDK type bindings for Azure Service Bus, which lets you work with data using these underlying SDK types:
617617

618618
+ [`ServiceBusReceivedMessage`](/python/api/azure-servicebus/azure.servicebus.servicebusreceivedmessage?view=azure-python)
619619

‎articles/azure-functions/functions-bindings-storage-blob-input.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -476,7 +476,7 @@ Access the blob data via a parameter that matches the name designated by binding
476476
::: zone pivot="programming-language-python"
477477
Access blob data via the parameter typed as [InputStream](/python/api/azure-functions/azure.functions.inputstream). Refer to the [input example](#example) for details.
478478

479-
Functions also supports Python SDK type bindings for Azure Blob storage, which lets you work with blob data using these underlying SDK types:
479+
Functions also support Python SDK type bindings for Azure Blob storage, which lets you work with blob data using these underlying SDK types:
480480

481481
+ [`BlobClient`](/python/api/azure-storage-blob/azure.storage.blob.blobclient)
482482
+ [`ContainerClient`](/python/api/azure-storage-blob/azure.storage.blob.containerclient)

0 commit comments

Comments
 (0)