You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: get-credhub-vars.html.md.erb
+21-21
Original file line number
Diff line number
Diff line change
@@ -18,10 +18,10 @@ Use these endpoints to view variables for any product in Ops Manager, except the
18
18
19
19
## <aid="fetch-variables"></a> Fetching variables
20
20
21
-
This endpoint returns the list of variables associated with a product that are stored in CredHub<!--฿ There are two CredHubs in PCF v2.0: BOSH CredHub and runtime CredHub. ฿-->. Not all variables are stored in CredHub<!--฿ There are two CredHubs in PCF v2.0: BOSH CredHub and runtime CredHub. ฿-->. If you call a variable that is not stored in CredHub<!--฿ There are two CredHubs in PCF v2.0: BOSH CredHub and runtime CredHub. ฿-->, the call returns an empty value.
21
+
This endpoint returns the list of variables associated with a product that are stored in CredHub. Not all variables are stored in CredHub. If you call a variable that is not stored in CredHub, the call returns an empty value.
22
22
23
23
<preclass="terminal">
24
-
$ curl "http<span>s</span>://OPS-MAN-FQDN/api<!--฿ |API| is preferred. ฿-->/v0/deployed/products/product-guid<!--฿ |GUID| is preferred. ฿-->/variables" \
This endpoint returns the value of a variable stored in CredHub<!--฿ There are two CredHubs in PCF v2.0: BOSH CredHub and runtime CredHub. ฿-->. Not all variables are stored in CredHub<!--฿ There are two CredHubs in PCF v2.0: BOSH CredHub and runtime CredHub. ฿-->, so if you call a variable that isn't in CredHub<!--฿ There are two CredHubs in PCF v2.0: BOSH CredHub and runtime CredHub. ฿-->, the call returns an empty value.
54
+
This endpoint returns the value of a variable stored in CredHub. Not all variables are stored in CredHub, so if you call a variable that isn't in CredHub, the call returns an empty value.
55
55
56
56
<preclass="terminal">
57
-
$ curl "http<span>s</span>://OPS-MAN-FQDN/api<!--฿ |API| is preferred. ฿-->/v0/deployed/products/product-guid<!--฿ |GUID| is preferred. ฿-->/variables?name=EXAMPLE-VARIABLE-NAME" \
Copy file name to clipboardexpand all lines: index.html.md.erb
+5-5
Original file line number
Diff line number
Diff line change
@@ -59,23 +59,23 @@ Depending on what you build, you must install the following tools:
59
59
60
60
- [Tile Generator](./tile-generator.html#-how-to-use): Used to package your software into a tile.
61
61
62
-
- [BOSH Command Line Interface (CLI)](https://bosh.io/docs/cli-v2/): A CLI for running BOSH commands. You need BOSH commands to run Tile Generator.
62
+
- [BOSH Command Line Interface (CLI)](https://bosh.io/docs/cli-v2/)<!--฿ Change the link name to |BOSH documentation|. ฿-->: A CLI for running BOSH commands. You need BOSH commands to run Tile Generator.
63
63
64
64
- [Cloud Foundry Command Line Interface (cf CLI)](https://github.com/cloudfoundry/cli#downloads): A CLI for deploying and managing apps on Cloud Foundry. If you are developing on Cloud Foundry, you use cf CLI when building your tile.
65
65
66
-
- [Kubernetes Command Line Tool (kubectl)](https://kubernetes.io/docs/tasks/tools/install-kubectl/) A CLI for deploying and managing apps on Kubernetes. If you are developing on Kubernetes, you use kubectl when building your tile.
66
+
- [Kubernetes Command Line Tool (kubectl)](https://kubernetes.io/docs/tasks/tools/install-kubectl/)<!--฿ Change the link name to |Kubernetes documentation|. ฿--> A CLI for deploying and managing apps on Kubernetes. If you are developing on Kubernetes, you use kubectl when building your tile.
67
67
68
68
- [CF Dev](https://github.com/cloudfoundry-incubator/cfdev) (optional): A lightweight <%=vars.app_runtime_full%> installation for deploying and debugging apps locally. You can use Cloud Foundry Dev to run <%=vars.app_runtime_abbr%> on your local workstation.
69
69
70
70
#### <aid="generate"></a> Step 2: Generate a tile
71
71
72
-
Tile Generator simplifies building tiles. To use Tile Generator, upload your software components, such as the service broker, buildpack, and Docker image, and the tool generates a base tile.
72
+
Tile Generator simplifies building tiles. To use Tile Generator, upload your software components, such as the service broker, buildpack, and Docker image,<!--฿ If a list, maybe reformat it as bullets. If this is a rambling sentence, break it up into smaller sentences. ฿--> and the tool generates a base tile.
73
73
74
74
For information about setting up Tile Generator and building a base tile, see [Tile Generator](./tile-generator.html).
75
75
76
76
#### <aid="test"></a> Step 3: Test your tile
77
77
78
-
Before you publish your tile, you can test it manually using a Partner Integration Environment (PIE). In PIE you can see how the tile functions on an IaaS, such as Amazon WebServices (AWS) or Google Cloud Platform (GCP). You can upload, configure, and install your tile in PIE as an operator does.
78
+
Before you publish your tile, you can test it manually using a Partner Integration Environment (PIE). In PIE you can see how the tile functions on an IaaS, such as Amazon Web<!--฿ Capitalize only when you use the term |World Wide Web|. Do not use |WWW|. Do not capitalize |the web|. ฿-->Services (AWS) or Google Cloud Platform <!--฿ Shorten to |GCP| after the first use. ฿-->(GCP). You can upload, configure, and install your tile in PIE as an operator does.
79
79
80
80
To gain access to your PIE, reach out to your contact at <%=vars.company_name%> or [register as a partner](https://partners.pivotal.io/).
81
81
@@ -124,4 +124,4 @@ Contact your <%= vars.company_name %> representative to guide you through upload
124
124
For information about the release cycle for Partner tiles, see [Partner Software Release Cycle](./releases.html).
125
125
126
126
## <aid="contact"></a> Support
127
-
To learn more about the VMware Tanzu ISV Partner Program or request help with your integration project, see [Contact Us](./contacts.html).
127
+
To learn more about the VMware Tanzu ISV Partner Program or request help with your integration project, see [Contact Us](./contacts.html)<!--฿ If this file is a partial, do not use relative links. ฿-->.
* [Types of integration](/docs-tiledev/stages.html)<!--฿ Do not start a relative link with a forward slash. ฿-->
9
+
* [User-provided service](/docs-tiledev/user-provided.html)<!--฿ Do not start a relative link with a forward slash. ฿-->
10
+
* [Creating a brokered service and service tile](/docs-tiledev/brokered.html)<!--฿ Do not start a relative link with a forward slash. ฿-->
11
+
* [**Managed services**](/docs-tiledev/managed-index.html)<!--฿ Do not start a relative link with a forward slash. ฿-->
12
+
* [About managed service](/docs-tiledev/managed.html)<!--฿ Do not start a relative link with a forward slash. ฿-->
13
+
* [BOSH release resources](/docs-tiledev/bosh-release.html)<!--฿ Do not start a relative link with a forward slash. ฿-->
14
+
* [Errands](/docs-tiledev/tile-errands.html)<!--฿ Do not start a relative link with a forward slash. ฿-->
15
+
* [On-demand service](/docs-tiledev/on-demand.html)<!--฿ Do not start a relative link with a forward slash. ฿-->
16
+
* [Resources for deploying your buildpacks](/docs-tiledev/buildpacks.html)<!--฿ Do not start a relative link with a forward slash. ฿-->
17
+
* [Embedded agents](/docs-tiledev/embedded-agents.html)<!--฿ Do not start a relative link with a forward slash. ฿-->
18
+
* [**CredHub**](/docs-tiledev/credhub-index.html)<!--฿ Do not start a relative link with a forward slash. ฿-->
19
+
* [CredHub](/docs-tiledev/credhub.html)<!--฿ Do not start a relative link with a forward slash. ฿-->
20
+
* [Creating new variables in CredHub](/docs-tiledev/create-credhub-vars.html)<!--฿ Do not start a relative link with a forward slash. ฿-->
21
+
* [Migrating existing credentials to CredHub](/docs-tiledev/migrating-credhub-credentials.html)<!--฿ Do not start a relative link with a forward slash. ฿-->
22
+
* [Fetching variable names and values](/docs-tiledev/get-credhub-vars.html)<!--฿ Do not start a relative link with a forward slash. ฿-->
23
+
* [Securing service credentials with Rrntime CredHub](/docs-tiledev/ssi-creds-tiledev.html)<!--฿ Do not start a relative link with a forward slash. ฿-->
24
+
* [How to integrate services with Cloud Foundry's logging system](/docs-tiledev/nozzle.html)<!--฿ Do not start a relative link with a forward slash. ฿-->
25
+
* [Syslog: migrating existing configuration](/docs-tiledev/migrating-syslog-configuration.html)<!--฿ If this file is a partial, do not use relative links. ฿--><!--฿ Do not start a relative link with a forward slash. ฿-->
Copy file name to clipboardexpand all lines: managed-index.html.md.erb
+1-1
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Integrating your managed services
3
3
owner: Services
4
4
---
5
5
6
-
Here's how to integrate your [brokered service](./brokered.html) more closely with <%= vars.platform_name %> to create a managed service and service tile for VMware Tanzu.
6
+
Here is how to integrate your [brokered service](./brokered.html) more closely with <%= vars.platform_name %> to create a managed service and service tile for VMware Tanzu.
Copy file name to clipboardexpand all lines: managed.html.md.erb
+2-2
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: How to integrate your managed services
3
3
owner: Services
4
4
---
5
5
6
-
Here's how to integrate your [brokered service](./brokered.html) more closely with <%= vars.platform_name %> to create a managed service and service tile for VMware Tanzu.
6
+
Here is how to integrate your [brokered service](./brokered.html) more closely with <%= vars.platform_name %> to create a managed service and service tile for VMware Tanzu.
7
7
8
8
## <aid="overview"></a> Managed services overview
9
9
@@ -23,7 +23,7 @@ To integrate your service at this level, you configure to learn about stemcells,
For a Minimal Viable Product (MVP) version of a managed service, you should aim for a single, shared service instance, and don't yet
26
+
Minimal Viable Product (MVP) version of a managed service should aim for a single, shared service instance, and don't yet
27
27
worry too much about High Availability of this instance. This integration level is mostly about getting the BOSH packaging, deployment, and monitoring working
Copy file name to clipboardexpand all lines: migrating-credhub-credentials.html.md.erb
+3-3
Original file line number
Diff line number
Diff line change
@@ -3,7 +3,7 @@ title: Migrating existing credentials to CredHub
3
3
owner: CredHub
4
4
---
5
5
6
-
Here's how to migrate non-configurable secrets from Ops Manager into CredHub.
6
+
Here is how to migrate non-configurable secrets from Ops Manager into CredHub.
7
7
8
8
## <aid="cred-types"></a>CredHub credential types
9
9
@@ -51,7 +51,7 @@ Tile authors can write a JavaScript migration to move their existing non-configu
51
51
52
52
1. Use the following example to write the JavaScript migration.
53
53
Save the JavaScript file to the `PRODUCT/migrations/v1` directory of your `.pivotal` tile,
54
-
following the naming conventions discussed in the [Update Values or Property Names Using JavaScript](./tile-upgrades.html) topic.
54
+
following the naming conventionsx in the [Update Values or Property Names Using JavaScript](./tile-upgrades.html) topic.
55
55
56
56
```js
57
57
exports.migrate = function(input) {
@@ -63,7 +63,7 @@ following the naming conventions discussed in the [Update Values or Property Nam
63
63
};
64
64
```
65
65
66
-
In the code block above, replace the example text as follows:
66
+
Replace the example text as follows:
67
67
68
68
* `PROPERTY-REFERENCE`: Replace with the property reference that corresponds to the metadata file, such as `properties`. See [Tile Upgrades](./tile-upgrades.html#import) for more information about migrating properties.
69
69
* `EXAMPLE-SECRET`: Replace with the name of the key.
Copy file name to clipboardexpand all lines: nozzle.html.md.erb
+1-1
Original file line number
Diff line number
Diff line change
@@ -79,7 +79,7 @@ Do so with the following properties:
79
79
A nozzle is a component dedicated to reading and processing data that streams from Firehose.
80
80
A service tile can install a nozzle as either a managed service, with package type `bosh-release`, or as an app pushed to <%=vars.app_runtime_abbr%>, with the package type `app`.
Copy file name to clipboardexpand all lines: odb-resource-defaults.html.md.erb
+4-5
Original file line number
Diff line number
Diff line change
@@ -8,18 +8,17 @@ owner: Ops Manager
8
8
Ops Manager 2.0 and later supports defining VM and disk type defaults and constraints.
9
9
</p>
10
10
11
+
Here is how tile authors can configure the drop-down menu menu items for VM types and persistent disk types in their tile.
11
12
12
-
Here you find how tile authors can configure the dropdown menu items for VM types and persistent disk types in their tile.
13
-
14
-
On-demand service tiles have a configuration pane for each service plan.
15
-
Operators use dropdown menus on the plan configuration pane to set the VM type and persistent disk type for each instance of that plan.
13
+
On-Demand service tiles have a configuration pane for each service plan.
14
+
Operators use drop-down menus on the plan configuration pane to set the VM type and persistent disk type for each instance of that plan.
16
15
17
16
Ops Manager populates the menus with options based on the VM and disk options available on the current IaaS.
18
17
Setting default values for VMs and disk types helps operators to select the right resources for on-demand service broker (ODB) services when using on-demand plans.
19
18
20
19
## <aid="defaults"></a>VM and Persistent disk types
21
20
22
-
The property that defines the VM type options is `vm_type_dropdown`, and the menu options for disk type come from the `disk_type_dropdown` property.
21
+
The property that defines the VM type options is `vm_type_dropdown`, and the menu items for disk type come from the `disk_type_dropdown` property.
23
22
Tile authors do not specify the menu items in the product template.
24
23
25
24
Because VM and disk options differ by IaaS, Ops Manager uses a best-fit algorithm to match defaults to their closest equivalents on the IaaS, similar to how the **Resource Config** pane handles its **VM Type** and **Persistent Disk Type** options.
0 commit comments