dapr
/
docs
mirror of https://github.com/dapr/docs.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

Merge branch 'v1.9' into endgame_v1.9

This commit is contained in:
Hannah Hunter 2023-02-15 13:30:49 -06:00 committed by GitHub
parent 787ae17e60 590e36336b
commit 0383b2f8d3
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
3 changed files with 9 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

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

@ -304,11 +304,13 @@ Run the `order-processor` service alongside a Dapr sidecar.
dapr run --app-port 7001 --app-id order-processor --app-protocol http --dapr-http-port 3501 -- dotnet run
```
Below is the working code block from the order processor's `Program.cs` file.
```csharp
app.MapPost("/orders", async context => {
var data = await context.Request.ReadFromJsonAsync<Order>();
Console.WriteLine("Order received : " + data);
await context.Response.WriteAsync(data.ToString());
app.MapPost("/orders", (Order order) =>
{
Console.WriteLine("Order received : " + order);
return order.ToString();
});
```
@ -334,7 +336,7 @@ Run the `checkout` service alongside a Dapr sidecar.
dapr run --app-id checkout --app-protocol http --dapr-http-port 3500 -- dotnet run
```
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.
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.
```csharp
var client = new HttpClient();

2
daprdocs/content/en/operations/security/mtls.md
View File

@ -447,7 +447,7 @@ Tell the Sentry service where to load the certificates from using the `--issuer-
The next examples creates root and issuer certs and loads them with the Sentry service.
*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)*
*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)*
Create the root certificate:

2
daprdocs/content/en/operations/security/oauth.md
View File

@ -12,7 +12,7 @@ When the middleware is enabled any method invocation through Dapr needs to be au
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.
## Register your application with a authorization server
## Register your application with an authorization server
Different authorization servers provide different application registration experiences. Here are some samples:
<!-- IGNORE_LINKS -->