mirror of https://github.com/dapr/docs.git
Merge remote-tracking branch 'upstream/v1.5' into v1.5
This commit is contained in:
commit
8a90f9706a
|
@ -30,8 +30,8 @@
|
|||
}
|
||||
|
||||
@include media-breakpoint-up(md) {
|
||||
& > ul {
|
||||
padding-left: .5rem;
|
||||
& .ul-1 ul {
|
||||
padding-left: 1.5em;
|
||||
}
|
||||
}
|
||||
|
||||
|
@ -85,7 +85,22 @@
|
|||
|
||||
& > .td-sidebar-nav__section {
|
||||
padding-top: .5rem;
|
||||
padding-left: 0rem;
|
||||
padding-left: 1.5rem;
|
||||
}
|
||||
|
||||
li i { // Layout of icons
|
||||
padding-right: 0.5em;
|
||||
&:before{
|
||||
display: inline-block;
|
||||
text-align: center;
|
||||
min-width: 1em;
|
||||
}
|
||||
}
|
||||
|
||||
.td-sidebar-link.tree-root{
|
||||
font-weight: $font-weight-bold;
|
||||
color: $td-sidebar-tree-root-color;
|
||||
margin-bottom: 1rem;
|
||||
}
|
||||
}
|
||||
|
||||
|
@ -93,8 +108,7 @@
|
|||
@include media-breakpoint-up(md) {
|
||||
padding-top: 4rem;
|
||||
background-color: $td-sidebar-bg-color;
|
||||
padding-right: .5rem;
|
||||
padding-left: .5rem;
|
||||
padding-right: 1rem;
|
||||
border-right: 1px solid $td-sidebar-border-color;
|
||||
}
|
||||
|
||||
|
@ -144,4 +158,4 @@
|
|||
#content-desktop {display: none;}
|
||||
#content-mobile {display: block;}
|
||||
}
|
||||
}
|
||||
}
|
||||
|
|
|
@ -0,0 +1,18 @@
|
|||
---
|
||||
type: docs
|
||||
title: "Configuration overview"
|
||||
linkTitle: "Configuration overview"
|
||||
weight: 1000
|
||||
description: "Use Dapr to get and watch application configuration"
|
||||
---
|
||||
|
||||
Consuming application configuration is a common task when writing applications and frequently configuration stores are used to manage this configuration data. A configuration item is often dynamic in nature and is tightly coupled to the needs of the application that consumes it. For example, common uses for application configuration include names of secrets that need to be retrieved, different identifiers, partition or consumer IDs, names of databased to connect to etc. These configuration items are typically stored as key-value items in a database.
|
||||
|
||||
Dapr provides a [State Management API]({{<ref "state-management-overview.md">}}) that is based on key-value stores. However, application configuration can be changed by either developers or operators at runtime and the developer needs to be notified of these changes in order to take the required action and load the new configuration. Also the configuration data may want to be read only. Dapr's Configuration API allows developers to consume configuration items that are returned as key/value pair and subscribe to changes whenever a configuration item changes.
|
||||
|
||||
*This API is currently in `Alpha state` and only available on gRPC. An HTTP1.1 supported version with this URL `/v1.0/configuration` will be available before the API becomes stable.*
|
||||
|
||||
## References
|
||||
|
||||
- [How-To: Manage application configuration]({{< ref howto-manage-configuration.md >}})
|
||||
|
|
@ -50,9 +50,7 @@ with DaprClient() as d:
|
|||
pubsub_name='pubsub',
|
||||
topic='TOPIC_A',
|
||||
data=json.dumps(req_data),
|
||||
metadata=(
|
||||
('rawPayload', 'true')
|
||||
)
|
||||
publish_metadata={'rawPayload': 'true'}
|
||||
)
|
||||
# Print the request
|
||||
print(req_data, flush=True)
|
||||
|
|
|
@ -91,7 +91,7 @@ curl -i -d '{ "message": "hello" }' \
|
|||
```
|
||||
|
||||
## Using namespaces with pub/sub
|
||||
Read [Pub/Sub and namespaces]({{< ref "component-scopes.md" >}}) for more information on scoping components.
|
||||
Read [Configure Pub/Sub components with multiple namespaces]({{< ref "pubsub-namespaces.md" >}}) for more information on using namespaces with pub/sub.
|
||||
|
||||
## Application access to components with scopes
|
||||
|
||||
|
@ -127,4 +127,4 @@ scopes:
|
|||
|
||||
- [Configure Pub/Sub components with multiple namespaces]({{< ref "pubsub-namespaces.md" >}})
|
||||
- [Use secret scoping]({{< ref "secrets-scopes.md" >}})
|
||||
- [Limit the secrets that can be read from secret stores]({{< ref "secret-scope.md" >}})
|
||||
- [Limit the secrets that can be read from secret stores]({{< ref "secret-scope.md" >}})
|
||||
|
|
|
@ -168,7 +168,7 @@ spec:
|
|||
```
|
||||
|
||||
## Control-plane configuration
|
||||
There is a single configuration file called `default` installed with the Dapr control plane system services that applies global settings. This is only set up when Dapr is deployed to Kubernetes.
|
||||
There is a single configuration file called `daprsystem` installed with the Dapr control plane system services that applies global settings. This is only set up when Dapr is deployed to Kubernetes.
|
||||
|
||||
### Control-plane configuration settings
|
||||
A Dapr control plane configuration can configure the following settings:
|
||||
|
|
|
@ -0,0 +1,11 @@
|
|||
---
|
||||
type: docs
|
||||
title: "Run Dapr in a serverless offering"
|
||||
linkTitle: "Serverless"
|
||||
weight: 3000
|
||||
description: "Learn how to run your Dapr applications on a serverless cloud offering"
|
||||
---
|
||||
|
||||
If you'd like to run your Dapr applications without managing any of the underlying infrasturcture such as VMs or Kubernetes, you can choose a serverless cloud offering. These platforms integrate with Dapr to make it easy to deploy and manage your applications.
|
||||
|
||||
## Offerings
|
Binary file not shown.
After Width: | Height: | Size: 47 KiB |
|
@ -0,0 +1,24 @@
|
|||
---
|
||||
type: docs
|
||||
title: "Azure Container Apps"
|
||||
linkTitle: "Azure Container Apps"
|
||||
description: "Learn how to run your Dapr applications on the Azure Container Apps serverless platform "
|
||||
---
|
||||
|
||||
[Azure Container Apps](https://docs.microsoft.com/azure/container-apps/overview) is a serverless application hosting service where users do not see nor manage any underlying VMs, orchestrators, or other cloud infrastructure. Azure Container Apps enables you to run your application code packaged in multiple containers and is unopinionated about runtimes or programming models that are used.
|
||||
|
||||
|
||||
Dapr is built-in to Container Apps, enabling you to use the Dapr API building blocks without any manual deployment of the Dapr runtime. You simply deploy your services with their Dapr components.
|
||||
|
||||
|
||||
{{< button text="Learn more" link="https://docs.microsoft.com/azure/container-apps/overview" newtab="true" >}}
|
||||
|
||||
## Tutorial
|
||||
|
||||
Visit the [Azure docs](https://docs.microsoft.com/azure/container-apps/microservices-dapr) to try out a microservices tutorial, where you'll deploy two Dapr-enabled applications to Azure Container Apps.
|
||||
|
||||
|
||||
|
||||
<img src="azure-container-apps-microservices-dapr.png" alt="Diagram of a Container Apps environment with two Dapr services" style="width:600px" >
|
||||
|
||||
{{< button text="Try out Dapr on Container Apps" link="https://docs.microsoft.com/azure/container-apps/microservices-dapr" newtab="true" >}}
|
|
@ -1,15 +1,15 @@
|
|||
{{ $links := .Site.Params.links }}
|
||||
<footer class="bg-dark py-7 row d-print-none">
|
||||
<div class="container-fluid mx-sm-5">
|
||||
<div class="container-fluid mx-sm-5" style="margin-top: 2rem;">
|
||||
<div class="row">
|
||||
<div class="col-6 col-sm-2 text-xs-center order-sm-2">
|
||||
<div class="col-6 col-sm-2 text-xs-center order-sm-2" style="margin-top: 1rem;">
|
||||
{{ with $links }}
|
||||
{{ with index . "user"}}
|
||||
{{ template "footer-links-block" . }}
|
||||
{{ end }}
|
||||
{{ end }}
|
||||
</div>
|
||||
<div class="col-6 col-sm-2 text-right text-xs-center order-sm-3">
|
||||
<div class="col-6 col-sm-2 text-right text-xs-center order-sm-3" style="margin-top: 1rem;">
|
||||
{{ with $links }}
|
||||
{{ with index . "developer"}}
|
||||
{{ template "footer-links-block" . }}
|
||||
|
@ -17,7 +17,6 @@
|
|||
{{ end }}
|
||||
</div>
|
||||
<div class="col-12 col-sm-6 text-center py-2 order-sm-2">
|
||||
{{ with .Site.Params }}<small class="text-white">© {{ .copyright }} {{ now.Year}} | {{ .distributed | markdownify }}</small>{{ end }}<br></br>
|
||||
{{ with .Site.Params }}<small class="text-white">© {{ now.Year}} {{ .trademark | markdownify }}</small>{{ end }}
|
||||
{{ if not .Site.Params.ui.footer_about_disable }}
|
||||
{{ with .Site.GetPage "about" }}<p class="mt-2"><a href="{{ .RelPermalink }}">{{ .Title }}</a></p>{{ end }}
|
||||
|
|
|
@ -1,47 +0,0 @@
|
|||
{{/* We cache this partial for bigger sites and set the active class client side. */}}
|
||||
{{ $shouldDelayActive := ge (len .Site.Pages) 2000 }}
|
||||
<div id="td-sidebar-menu" class="td-sidebar__inner{{ if $shouldDelayActive }} d-none{{ end }}">
|
||||
{{ if not .Site.Params.ui.sidebar_search_disable }}
|
||||
<form class="td-sidebar__search d-flex align-items-center">
|
||||
{{ partial "search-input.html" . }}
|
||||
<button class="btn btn-link td-sidebar__toggle d-md-none p-0 ml-3 fas fa-bars" type="button" data-toggle="collapse" data-target="#td-section-nav" aria-controls="td-docs-nav" aria-expanded="false" aria-label="Toggle section navigation">
|
||||
</button>
|
||||
</form>
|
||||
{{ end }}
|
||||
<nav class="collapse td-sidebar-nav pt-2 pl-4" id="td-section-nav">
|
||||
{{ if (gt (len .Site.Home.Translations) 0) }}
|
||||
<div class="nav-item dropdown d-block d-lg-none">
|
||||
{{ partial "navbar-lang-selector.html" . }}
|
||||
</div>
|
||||
{{ end }}
|
||||
{{ template "section-tree-nav-section" (dict "page" . "section" .Site.Home "delayActive" $shouldDelayActive) }}
|
||||
</nav>
|
||||
</div>
|
||||
{{ define "section-tree-nav-section" }}
|
||||
{{ $s := .section }}
|
||||
{{ $p := .page }}
|
||||
{{ $shouldDelayActive := .delayActive }}
|
||||
{{ $active := eq $p.CurrentSection $s }}
|
||||
{{ $show := or (not $p.Site.Params.ui.sidebar_menu_compact) ($p.IsDescendant $s) }}
|
||||
{{ $sid := $s.RelPermalink | anchorize }}
|
||||
<ul class="td-sidebar-nav__section pr-md-3">
|
||||
<li class="td-sidebar-nav__section-title">
|
||||
<a href="{{ $s.RelPermalink }}" class="align-left pl-0 pr-2{{ if not $show }} collapsed{{ end }}{{ if $active}} active{{ end }} td-sidebar-link td-sidebar-link__section">{{ $s.LinkTitle }}</a>
|
||||
</li>
|
||||
<ul>
|
||||
<li class="collapse {{ if $show }}show{{ end }}" id="{{ $sid }}">
|
||||
{{ $pages := where (union $s.Pages $s.Sections).ByWeight ".Params.toc_hide" "!=" true }}
|
||||
{{ $pages := $pages | first 50 }}
|
||||
{{ range $pages }}
|
||||
{{ if and (.IsPage) (not .Params.nomenu) }}
|
||||
{{ $mid := printf "m-%s" (.RelPermalink | anchorize) }}
|
||||
{{ $active := eq . $p }}
|
||||
<a class="td-sidebar-link td-sidebar-link__page {{ if and (not $shouldDelayActive) $active }} active{{ end }}" id="{{ $mid }}" href="{{ .RelPermalink }}">{{ .LinkTitle }}</a>
|
||||
{{ else if not .Params.toc_hide }}
|
||||
{{ template "section-tree-nav-section" (dict "page" $p "section" .) }}
|
||||
{{ end }}
|
||||
{{ end }}
|
||||
</li>
|
||||
</ul>
|
||||
</ul>
|
||||
{{ end }}
|
|
@ -1 +1 @@
|
|||
Subproject commit c36be07b2dcb9aa5aa01bad6ed0f8e111dd0452c
|
||||
Subproject commit 43361e98f128082158c479ecb94008f29dc8f4e0
|
Loading…
Reference in New Issue