Update docs for 1.0 RC1.
This commit is contained in:
2032
1.0.0.RC1/index.html
Normal file
2032
1.0.0.RC1/index.html
Normal file
File diff suppressed because it is too large
Load Diff
@@ -466,7 +466,7 @@ body.book #toc,body.book #preamble,body.book h1.sect0,body.book .sect1>h2{page-b
|
||||
<div id="preamble">
|
||||
<div class="sectionbody">
|
||||
<div class="paragraph">
|
||||
<p>© 2016 The original authors.</p>
|
||||
<p>© 2016-2017 The original authors.</p>
|
||||
</div>
|
||||
<div class="admonitionblock note">
|
||||
<table>
|
||||
@@ -628,7 +628,7 @@ the test cases). Example Maven configuration:</p>
|
||||
<pre class="highlight"><code class="language-xml" data-lang="xml"><parent>
|
||||
<groupId>org.springframework.boot</groupId>
|
||||
<artifactId>spring-boot-starter-parent</artifactId>
|
||||
<version>1.5.0.RELEASE</version>
|
||||
<version>1.5.2.RELEASE</version>
|
||||
<relativePath /> <!-- lookup parent from repository -->
|
||||
</parent>
|
||||
|
||||
@@ -1307,9 +1307,9 @@ wrapped_accessor: 46b6aebb-187f-932a-26d7-4f3d86a68319</code></pre>
|
||||
backend. The generic secret backend allows storage of arbitrary
|
||||
values as key-value store. A single context can store one or many
|
||||
key-value tuples. Contexts can be organized hierarchically.
|
||||
Spring Cloud Vault allows using the Application name set in
|
||||
<code>spring.application.name</code> and a default context name (<code>application</code>)
|
||||
in combination with active profiles.</p>
|
||||
Spring Cloud Vault allows using the Application name
|
||||
and a default context name (<code>application</code>) in combination with active
|
||||
profiles.</p>
|
||||
</div>
|
||||
<div class="listingblock">
|
||||
<div class="content">
|
||||
@@ -1320,9 +1320,45 @@ in combination with active profiles.</p>
|
||||
</div>
|
||||
</div>
|
||||
<div class="paragraph">
|
||||
<p>The application name is determined by the properties:</p>
|
||||
</div>
|
||||
<div class="ulist">
|
||||
<ul>
|
||||
<li>
|
||||
<p><code>spring.cloud.vault.generic.application-name</code></p>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>spring.cloud.vault.application-name</code></p>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>spring.application.name</code></p>
|
||||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
<div class="paragraph">
|
||||
<p>Secrets can be obtained from other folders within the generic backend by adding their
|
||||
paths to the application name, separated by commas. For example, given the application
|
||||
name <code>usefulapp,mysql1,projectx/aws</code>, each of these folders will be used:</p>
|
||||
</div>
|
||||
<div class="ulist">
|
||||
<ul>
|
||||
<li>
|
||||
<p><code>/secret/usefulapp</code></p>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>/secret/mysql1</code></p>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>/secret/projectx/aws</code></p>
|
||||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
<div class="paragraph">
|
||||
<p>Spring Cloud Vault adds all active profiles to the list of possible context paths.
|
||||
No active profiles will skip accessing contexts with a profile name. Properties
|
||||
are exposed like they are stored (i.e. without additional prefixes).</p>
|
||||
No active profiles will skip accessing contexts with a profile name.</p>
|
||||
</div>
|
||||
<div class="paragraph">
|
||||
<p>Properties are exposed like they are stored (i.e. without additional prefixes).</p>
|
||||
</div>
|
||||
<div class="exampleblock">
|
||||
<div class="content">
|
||||
@@ -1332,8 +1368,9 @@ are exposed like they are stored (i.e. without additional prefixes).</p>
|
||||
generic:
|
||||
enabled: true
|
||||
backend: secret
|
||||
profile-separator: ','
|
||||
default-context: application</code></pre>
|
||||
profile-separator: '/'
|
||||
default-context: application
|
||||
application-name: my-app</code></pre>
|
||||
</div>
|
||||
</div>
|
||||
</div>
|
||||
@@ -1351,8 +1388,11 @@ config usage</p>
|
||||
<p><code>default-context</code> sets the context name used by all applications</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>profile-separator</code> sets the value of the separator used to separate the
|
||||
profile name in property sources with profiles</p>
|
||||
<p><code>application-name</code> overrides the application name for use in the generic backend</p>
|
||||
</li>
|
||||
<li>
|
||||
<p><code>profile-separator</code> separates the profile name from the context in
|
||||
property sources with profiles</p>
|
||||
</li>
|
||||
</ul>
|
||||
</div>
|
||||
|
||||
Reference in New Issue
Block a user