Skip to content

Commit 6879a62

Browse files
ggailey777ggailey777
committed
Swap with correct line endings (hopefully)
1 parent 5189bee commit 6879a62

15 files changed

+95
-95
lines changed

‎articles/azure-functions/functions-bindings-event-grid-output.md

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

526526
The attribute's constructor takes the name of an application setting that contains the name of the custom topic, and the name of an application setting that contains the topic key.
527527

528-
# [In-process model](#tab/in-process)
528+
# [Isolated worker model](#tab/isolated-process)
529529

530-
The following table explains the parameters for the `EventGridAttribute`.
530+
The following table explains the parameters for the `EventGridOutputAttribute`.
531531

532532
|Parameter | Description|
533533
|---------|---------|
534534
|**TopicEndpointUri** | The name of an app setting that contains the URI for the custom topic, such as `MyTopicEndpointUri`. |
535535
|**TopicKeySetting** | The name of an app setting that contains an access key for the custom topic. |
536-
|**Connection**<sup>*</sup> | The value of the common prefix for the setting that contains the topic endpoint URI. For more information about the naming format of this application setting, see [Identity-based authentication](#identity-based-authentication). |
536+
|**connection**<sup>*</sup> | The value of the common prefix for the setting that contains the topic endpoint URI. For more information about the naming format of this application setting, see [Identity-based authentication](#identity-based-authentication). |
537537

538-
# [Isolated worker model](#tab/isolated-process)
538+
# [In-process model](#tab/in-process)
539539

540-
The following table explains the parameters for the `EventGridOutputAttribute`.
540+
The following table explains the parameters for the `EventGridAttribute`.
541541

542542
|Parameter | Description|
543543
|---------|---------|
544544
|**TopicEndpointUri** | The name of an app setting that contains the URI for the custom topic, such as `MyTopicEndpointUri`. |
545545
|**TopicKeySetting** | The name of an app setting that contains an access key for the custom topic. |
546-
|**connection**<sup>*</sup> | The value of the common prefix for the setting that contains the topic endpoint URI. For more information about the naming format of this application setting, see [Identity-based authentication](#identity-based-authentication). |
546+
|**Connection**<sup>*</sup> | The value of the common prefix for the setting that contains the topic endpoint URI. For more information about the naming format of this application setting, see [Identity-based authentication](#identity-based-authentication). |
547547

548548
---
549549

‎articles/azure-functions/functions-bindings-event-hubs-output.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -246,18 +246,18 @@ In the [Java functions runtime library](/java/api/overview/azure/functions/runti
246246

247247
Both [in-process](functions-dotnet-class-library.md) and [isolated worker process](dotnet-isolated-process-guide.md) C# libraries use attribute to configure the binding. C# script instead uses a function.json configuration file as described in the [C# scripting guide](./functions-reference-csharp.md#event-hubs-output).
248248

249-
# [In-process model](#tab/in-process)
249+
# [Isolated worker model](#tab/isolated-process)
250250

251-
Use the [EventHubAttribute] to define an output binding to an event hub, which supports the following properties.
251+
Use the [EventHubOutputAttribute] to define an output binding to an event hub, which supports the following properties.
252252

253253
| Parameters | Description|
254254
|---------|----------------------|
255255
|**EventHubName** | The name of the event hub. When the event hub name is also present in the connection string, that value overrides this property at runtime. |
256256
|**Connection** | The name of an app setting or setting collection that specifies how to connect to Event Hubs. To learn more, see [Connections](#connections).|
257257

258-
# [Isolated worker model](#tab/isolated-process)
258+
# [In-process model](#tab/in-process)
259259

260-
Use the [EventHubOutputAttribute] to define an output binding to an event hub, which supports the following properties.
260+
Use the [EventHubAttribute] to define an output binding to an event hub, which supports the following properties.
261261

262262
| Parameters | Description|
263263
|---------|----------------------|

‎articles/azure-functions/functions-bindings-http-webhook-trigger.md

Lines changed: 5 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -501,26 +501,26 @@ def main(req: func.HttpRequest) -> func.HttpResponse:
501501

502502
Both [in-process](functions-dotnet-class-library.md) and [isolated worker process](dotnet-isolated-process-guide.md) C# libraries use the `HttpTriggerAttribute` to define the trigger binding. C# script instead uses a function.json configuration file as described in the [C# scripting guide](./functions-reference-csharp.md#http-trigger).
503503

504-
# [In-process model](#tab/in-process)
504+
# [Isolated worker model](#tab/isolated-process)
505505

506-
In [in-process functions](functions-dotnet-class-library.md), the `HttpTriggerAttribute` supports the following parameters:
506+
In [isolated worker process](dotnet-isolated-process-guide.md) function apps, the `HttpTriggerAttribute` supports the following parameters:
507507

508508
| Parameters | Description|
509509
|---------|----------------------|
510510
| **AuthLevel** | Determines what keys, if any, need to be present on the request in order to invoke the function. For supported values, see [Authorization level](#http-auth). |
511511
| **Methods** | An array of the HTTP methods to which the function responds. If not specified, the function responds to all HTTP methods. See [customize the HTTP endpoint](#customize-the-http-endpoint). |
512512
| **Route** | Defines the route template, controlling to which request URLs your function responds. The default value if none is provided is `<functionname>`. For more information, see [customize the HTTP endpoint](#customize-the-http-endpoint). |
513-
| **WebHookType** | _Supported only for the version 1.x runtime._<br/><br/>Configures the HTTP trigger to act as a [webhook](https://en.wikipedia.org/wiki/Webhook) receiver for the specified provider. For supported values, see [WebHook type](#webhook-type).|
514513

515-
# [Isolated worker model](#tab/isolated-process)
514+
# [In-process model](#tab/in-process)
516515

517-
In [isolated worker process](dotnet-isolated-process-guide.md) function apps, the `HttpTriggerAttribute` supports the following parameters:
516+
In [in-process functions](functions-dotnet-class-library.md), the `HttpTriggerAttribute` supports the following parameters:
518517

519518
| Parameters | Description|
520519
|---------|----------------------|
521520
| **AuthLevel** | Determines what keys, if any, need to be present on the request in order to invoke the function. For supported values, see [Authorization level](#http-auth). |
522521
| **Methods** | An array of the HTTP methods to which the function responds. If not specified, the function responds to all HTTP methods. See [customize the HTTP endpoint](#customize-the-http-endpoint). |
523522
| **Route** | Defines the route template, controlling to which request URLs your function responds. The default value if none is provided is `<functionname>`. For more information, see [customize the HTTP endpoint](#customize-the-http-endpoint). |
523+
| **WebHookType** | _Supported only for the version 1.x runtime._<br/><br/>Configures the HTTP trigger to act as a [webhook](https://en.wikipedia.org/wiki/Webhook) receiver for the specified provider. For supported values, see [WebHook type](#webhook-type).|
524524

525525
---
526526

‎articles/azure-functions/functions-bindings-sendgrid.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -315,9 +315,9 @@ public class HttpTriggerSendGrid {
315315

316316
Both [in-process](functions-dotnet-class-library.md) and [isolated worker process](dotnet-isolated-process-guide.md) C# libraries use attributes to define the output binding. C# script instead uses a function.json configuration file.
317317

318-
# [In-process model](#tab/in-process)
318+
# [Isolated worker model](#tab/isolated-process)
319319

320-
In [in-process](functions-dotnet-class-library.md) function apps, use the [SendGridAttribute](https://github.com/Azure/azure-webjobs-sdk-extensions/blob/master/src/WebJobs.Extensions.SendGrid/SendGridAttribute.cs), which supports the following parameters.
320+
In [isolated worker process](dotnet-isolated-process-guide.md) function apps, the `SendGridOutputAttribute` supports the following parameters:
321321

322322
| Attribute/annotation property | Description |
323323
|-------------------------------|-------------|
@@ -327,9 +327,9 @@ In [in-process](functions-dotnet-class-library.md) function apps, use the [SendG
327327
| **Subject** | (Optional) The subject of the email. |
328328
| **Text** | (Optional) The email content. |
329329

330-
# [Isolated worker model](#tab/isolated-process)
330+
# [In-process model](#tab/in-process)
331331

332-
In [isolated worker process](dotnet-isolated-process-guide.md) function apps, the `SendGridOutputAttribute` supports the following parameters:
332+
In [in-process](functions-dotnet-class-library.md) function apps, use the [SendGridAttribute](https://github.com/Azure/azure-webjobs-sdk-extensions/blob/master/src/WebJobs.Extensions.SendGrid/SendGridAttribute.cs), which supports the following parameters.
333333

334334
| Attribute/annotation property | Description |
335335
|-------------------------------|-------------|

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

Lines changed: 12 additions & 12 deletions
Original file line numberDiff line numberDiff line change
@@ -293,6 +293,18 @@ def main(req: func.HttpRequest, msg: func.Out[str]) -> func.HttpResponse:
293293

294294
Both [in-process](functions-dotnet-class-library.md) and [isolated worker process](dotnet-isolated-process-guide.md) C# libraries use attributes to define the output binding. C# script instead uses a function.json configuration file as described in the [C# scripting guide](./functions-reference-csharp.md#service-bus-output).
295295

296+
# [Isolated worker model](#tab/isolated-process)
297+
298+
In [C# class libraries](dotnet-isolated-process-guide.md), use the [ServiceBusOutputAttribute](https://github.com/Azure/azure-functions-dotnet-worker/blob/main/extensions/Worker.Extensions.ServiceBus/src/ServiceBusOutputAttribute.cs) to define the queue or topic written to by the output.
299+
300+
The following table explains the properties you can set using the attribute:
301+
302+
| Property |Description|
303+
| --- | --- |
304+
|**EntityType**|Sets the entity type as either `Queue` for sending messages to a queue or `Topic` when sending messages to a topic. |
305+
|**QueueOrTopicName**|Name of the topic or queue to send messages to. Use `EntityType` to set the destination type.|
306+
|**Connection**|The name of an app setting or setting collection that specifies how to connect to Service Bus. See [Connections](#connections).|
307+
296308
# [In-process model](#tab/in-process)
297309

298310
In [C# class libraries](functions-dotnet-class-library.md), use the [ServiceBusAttribute](https://github.com/Azure/azure-functions-servicebus-extension/blob/master/src/Microsoft.Azure.WebJobs.Extensions.ServiceBus/ServiceBusAttribute.cs).
@@ -332,18 +344,6 @@ For a complete example, see [Example](#example).
332344

333345
You can use the `ServiceBusAccount` attribute to specify the Service Bus account to use at class, method, or parameter level. For more information, see [Attributes](functions-bindings-service-bus-trigger.md#attributes) in the trigger reference.
334346

335-
# [Isolated worker model](#tab/isolated-process)
336-
337-
In [C# class libraries](dotnet-isolated-process-guide.md), use the [ServiceBusOutputAttribute](https://github.com/Azure/azure-functions-dotnet-worker/blob/main/extensions/Worker.Extensions.ServiceBus/src/ServiceBusOutputAttribute.cs) to define the queue or topic written to by the output.
338-
339-
The following table explains the properties you can set using the attribute:
340-
341-
| Property |Description|
342-
| --- | --- |
343-
|**EntityType**|Sets the entity type as either `Queue` for sending messages to a queue or `Topic` when sending messages to a topic. |
344-
|**QueueOrTopicName**|Name of the topic or queue to send messages to. Use `EntityType` to set the destination type.|
345-
|**Connection**|The name of an app setting or setting collection that specifies how to connect to Service Bus. See [Connections](#connections).|
346-
347347
---
348348

349349
::: zone-end

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

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -345,7 +345,7 @@ def main(msg: azf.ServiceBusMessage) -> str:
345345

346346
Both [in-process](functions-dotnet-class-library.md) and [isolated worker process](dotnet-isolated-process-guide.md) C# libraries use the [ServiceBusTriggerAttribute](https://github.com/Azure/azure-functions-servicebus-extension/blob/master/src/Microsoft.Azure.WebJobs.Extensions.ServiceBus/ServiceBusTriggerAttribute.cs) attribute to define the function trigger. C# script instead uses a function.json configuration file as described in the [C# scripting guide](./functions-reference-csharp.md#service-bus-trigger).
347347

348-
# [In-process model](#tab/in-process)
348+
# [Isolated worker model](#tab/isolated-process)
349349

350350
The following table explains the properties you can set using this trigger attribute:
351351

@@ -355,12 +355,10 @@ The following table explains the properties you can set using this trigger attri
355355
|**TopicName**|Name of the topic to monitor. Set only if monitoring a topic, not for a queue.|
356356
|**SubscriptionName**|Name of the subscription to monitor. Set only if monitoring a topic, not for a queue.|
357357
|**Connection**| The name of an app setting or setting collection that specifies how to connect to Service Bus. See [Connections](#connections).|
358-
|**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.|
359358
|**IsBatched**| Messages are delivered in batches. Requires an array or collection type. |
360359
|**IsSessionsEnabled**|`true` if connecting to a [session-aware](../service-bus-messaging/message-sessions.md) queue or subscription. `false` otherwise, which is the default value.|
361-
|**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 [MessageReceiver](/dotnet/api/microsoft.azure.servicebus.core.messagereceiver) methods to complete, abandon, or deadletter the message. If an exception is thrown (and none of the `MessageReceiver` 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. |
362360

363-
# [Isolated worker model](#tab/isolated-process)
361+
# [In-process model](#tab/in-process)
364362

365363
The following table explains the properties you can set using this trigger attribute:
366364

@@ -370,8 +368,10 @@ The following table explains the properties you can set using this trigger attri
370368
|**TopicName**|Name of the topic to monitor. Set only if monitoring a topic, not for a queue.|
371369
|**SubscriptionName**|Name of the subscription to monitor. Set only if monitoring a topic, not for a queue.|
372370
|**Connection**| The name of an app setting or setting collection that specifies how to connect to Service Bus. See [Connections](#connections).|
371+
|**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.|
373372
|**IsBatched**| Messages are delivered in batches. Requires an array or collection type. |
374373
|**IsSessionsEnabled**|`true` if connecting to a [session-aware](../service-bus-messaging/message-sessions.md) queue or subscription. `false` otherwise, which is the default value.|
374+
|**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 [MessageReceiver](/dotnet/api/microsoft.azure.servicebus.core.messagereceiver) methods to complete, abandon, or deadletter the message. If an exception is thrown (and none of the `MessageReceiver` 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. |
375375

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

‎articles/azure-functions/functions-bindings-signalr-service-input.md

Lines changed: 4 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -251,9 +251,9 @@ public SignalRConnectionInfo negotiate(
251251

252252
Both [in-process](functions-dotnet-class-library.md) and [isolated worker process](dotnet-isolated-process-guide.md) C# libraries use attribute to define the function. C# script instead uses a function.json configuration file.
253253

254-
# [In-process model](#tab/in-process)
254+
# [Isolated worker model](#tab/isolated-process)
255255

256-
The following table explains the properties of the `SignalRConnectionInfo` attribute:
256+
The following table explains the properties of the `SignalRConnectionInfoInput` attribute:
257257

258258
| Attribute property |Description|
259259
|---------|----------------------|
@@ -263,9 +263,9 @@ The following table explains the properties of the `SignalRConnectionInfo` attri
263263
|**IdToken**| Optional. A JWT token whose claims will be added to the user claims. It should be used together with **ClaimTypeList**. You can use a [binding expression](#binding-expressions-for-http-trigger) to bind the value to an HTTP request header or query. |
264264
|**ClaimTypeList**| Optional. A list of claim types, which filter the claims in **IdToken** . |
265265

266-
# [Isolated worker model](#tab/isolated-process)
266+
# [In-process model](#tab/in-process)
267267

268-
The following table explains the properties of the `SignalRConnectionInfoInput` attribute:
268+
The following table explains the properties of the `SignalRConnectionInfo` attribute:
269269

270270
| Attribute property |Description|
271271
|---------|----------------------|

‎articles/azure-functions/functions-bindings-signalr-service-output.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -512,24 +512,24 @@ public SignalRGroupAction removeFromGroup(
512512

513513
Both [in-process](functions-dotnet-class-library.md) and [isolated worker process](dotnet-isolated-process-guide.md) C# libraries use attribute to define the function. C# script instead uses a [function.json configuration file](#configuration).
514514

515-
# [In-process model](#tab/in-process)
515+
# [Isolated worker model](#tab/isolated-process)
516516

517-
The following table explains the properties of the `SignalR` output attribute.
517+
The following table explains the properties of the `SignalROutput` attribute.
518518

519519
| Attribute property |Description|
520520
|---------|----------------------|
521521
|**HubName**| This value must be set to the name of the SignalR hub for which the connection information is generated.|
522522
|**ConnectionStringSetting**| The name of the app setting that contains the SignalR Service connection string, which defaults to `AzureSignalRConnectionString`. |
523+
# [In-process model](#tab/in-process)
523524

524-
525-
# [Isolated worker model](#tab/isolated-process)
526-
527-
The following table explains the properties of the `SignalROutput` attribute.
525+
The following table explains the properties of the `SignalR` output attribute.
528526

529527
| Attribute property |Description|
530528
|---------|----------------------|
531529
|**HubName**| This value must be set to the name of the SignalR hub for which the connection information is generated.|
532530
|**ConnectionStringSetting**| The name of the app setting that contains the SignalR Service connection string, which defaults to `AzureSignalRConnectionString`. |
531+
532+
533533
---
534534

535535
::: zone-end

0 commit comments

Comments
 (0)