Skip to content

Commit 0383b2f

Browse files
authored
Merge branch 'v1.9' into endgame_v1.9
2 parents 787ae17 + 590e363 commit 0383b2f

File tree

3 files changed

+9
-7
lines changed

3 files changed

+9
-7
lines changed

daprdocs/content/en/getting-started/quickstarts/serviceinvocation-quickstart.md

Lines changed: 7 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -304,11 +304,13 @@ Run the `order-processor` service alongside a Dapr sidecar.
304304
dapr run --app-port 7001 --app-id order-processor --app-protocol http --dapr-http-port 3501 -- dotnet run
305305
```
306306

307+
Below is the working code block from the order processor's `Program.cs` file.
308+
307309
```csharp
308-
app.MapPost("/orders", async context => {
309-
var data = await context.Request.ReadFromJsonAsync<Order>();
310-
Console.WriteLine("Order received : " + data);
311-
await context.Response.WriteAsync(data.ToString());
310+
app.MapPost("/orders", (Order order) =>
311+
{
312+
Console.WriteLine("Order received : " + order);
313+
return order.ToString();
312314
});
313315
```
314316

@@ -334,7 +336,7 @@ Run the `checkout` service alongside a Dapr sidecar.
334336
dapr run --app-id checkout --app-protocol http --dapr-http-port 3500 -- dotnet run
335337
```
336338

337-
In the `checkout` service, you'll notice there's no need to rewrite your app code to use Dapr's service invocation. You can enable service invocation by simply adding the `dapr-app-id` header, which specifies the ID of the target service.
339+
In the Program.cs file for the `checkout` service, you'll notice there's no need to rewrite your app code to use Dapr's service invocation. You can enable service invocation by simply adding the `dapr-app-id` header, which specifies the ID of the target service.
338340

339341
```csharp
340342
var client = new HttpClient();

daprdocs/content/en/operations/security/mtls.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -447,7 +447,7 @@ Tell the Sentry service where to load the certificates from using the `--issuer-
447447

448448
The next examples creates root and issuer certs and loads them with the Sentry service.
449449

450-
*Note: This example uses the step tool to create the certificates. You can install step tool from [here](https://smallstep.com/docs/getting-started/). Windows binaries available [here](https://github.com/smallstep/cli/releases)*
450+
*Note: This example uses the step tool to create the certificates. You can install step tool from [here](https://smallstep.com/docs/step-cli/installation). Windows binaries available [here](https://github.com/smallstep/cli/releases)*
451451

452452
Create the root certificate:
453453

daprdocs/content/en/operations/security/oauth.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ When the middleware is enabled any method invocation through Dapr needs to be au
1212

1313
The main difference between the two flows is that the `Authorization Code Grant flow` needs user interaction and authorizes a user where the `Client Credentials Grant flow` doesn't need a user interaction and authorizes a service/application.
1414

15-
## Register your application with a authorization server
15+
## Register your application with an authorization server
1616

1717
Different authorization servers provide different application registration experiences. Here are some samples:
1818
<!-- IGNORE_LINKS -->

0 commit comments

Comments
 (0)