upperBound) {
+ throw new NumberFormatException("Value must be at most "+upperBound);
+ }
+ return value;
+ }
+ };
+ }
+
+}
diff --git a/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/buildpack.html b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/buildpack.html
new file mode 100644
index 000000000..2f3fb4cb2
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/buildpack.html
@@ -0,0 +1,11 @@
+If your application requires a custom buildpack, you can use the buildpack attribute to specify its URL or name:
+
+
+---
+ ...
+ buildpack: buildpack_URL
+
+
+Note: The cf buildpacks command lists the buildpacks that you can refer to by name in a manifest or a command line option.
+
+The command line option that overrides this attribute is -b.
diff --git a/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/buildpack.md b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/buildpack.md
new file mode 100644
index 000000000..afc713276
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/buildpack.md
@@ -0,0 +1,11 @@
+If your application requires a custom buildpack, you can use the `buildpack` attribute to specify its URL or name:
+
+```
+---
+ ...
+ buildpack: buildpack_URL
+```
+
+**Note**: The `cf buildpacks` command lists the buildpacks that you can refer to by name in a manifest or a command line option.
+
+The command line option that overrides this attribute is `-b`.
diff --git a/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/command.html b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/command.html
new file mode 100644
index 000000000..aab1e4651
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/command.html
@@ -0,0 +1,34 @@
+Some languages and frameworks require that you provide a custom command to start an application. Refer to the buildpack documentation to determine if you need to provide a custom start command.
+
+You can provide the custom start command in your application manifest or on the command line.
+
+To specify the custom start command in your application manifest, add it in the command: START-COMMAND format as the following example shows:
+
+
+---
+ ...
+ command: bundle exec rake VERBOSE=true
+
+
+On the command line, use the -c option to specify the custom start command as the following example shows:
+
+
+$ cf push my-app -c "bundle exec rake VERBOSE=true"
+
+
+Note: The -c option with a value of ‘null’ forces cf push to use the buildpack start command. See About Starting Applications for more information.
+
+If you override the start command for a Buildpack application, Linux uses
+bash -c YOUR-COMMAND to invoke your application.
+If you override the start command for a Docker application, Linux uses sh -c YOUR-COMMAND to invoke your application.
+Because of this, if you override a start command, you should prefix exec to the final command in your custom composite start command.
+
+exec causes the last command to become the root process of your application. The Cloud Foundry Updates and Your Application section of the Considerations for Designing and Running an Application in the Cloud topic explains why your application should handle a termination signal during Cloud Foundry updates.
+Without an exec statement, the parent process remains as the implied bash process, and does not propagate signals to your application process.
+
+For example, both of the following composite start commands run database migrations when the first instance of the app starts, then start the app to serve requests, but they behave differently on graceful shutdown.
+
+
+bin/rake cf:on_first_instance db:migrate && bin/rails server -p $PORT -e $RAILS_ENV: The process tree is bash -> ruby, so on graceful shutdown only the bash process receives the TERM signal, and not the ruby process.
bin/rake cf:on_first_instance db:migrate && exec bin/rails server -p $PORT -e $RAILS_ENV: Because of the exec prefix on the final command, the ruby process invoked by rails takes over the bash process managing the execution of the composite command. The process tree is only ruby, so the ruby web server receives the TERM signal can shutdown gracefully for 10 seconds.
\ No newline at end of file
diff --git a/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/command.md b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/command.md
new file mode 100644
index 000000000..2d17d293a
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/command.md
@@ -0,0 +1,30 @@
+Some languages and frameworks require that you provide a custom command to start an application. Refer to the [buildpack](/buildpacks/) documentation to determine if you need to provide a custom start command.
+
+You can provide the custom start command in your application manifest or on the command line.
+
+To specify the custom start command in your application manifest, add it in the `command: START-COMMAND` format as the following example shows:
+
+
+```
+---
+ ...
+ command: bundle exec rake VERBOSE=true
+```
+
+On the command line, use the `-c` option to specify the custom start command as the following example shows:
+
+```
+$ cf push my-app -c "bundle exec rake VERBOSE=true"
+```
+
+**Note**: The `-c` option with a value of ‘null’ forces `cf push` to use the buildpack start command. See [About Starting Applications](./app-startup.html) for more information.
+
+If you override the start command for a Buildpack application, Linux uses `bash -c YOUR-COMMAND` to invoke your application. If you override the start command for a Docker application, Linux uses `sh -c YOUR-COMMAND` to invoke your application. Because of this, if you override a start command, you should prefix `exec` to the final command in your custom composite start command.
+
+`exec` causes the last command to become the root process of your application. The [Cloud Foundry Updates and Your Application](./prepare-to-deploy.html#moving-apps) section of the _Considerations for Designing and Running an Application in the Cloud_ topic explains why your application should handle a `termination signal` during Cloud Foundry updates. Without an `exec` statement, the parent process remains as the implied bash process, and does not propagate signals to your application process.
+
+For example, both of the following composite start commands run database migrations when the first instance of the app starts, then start the app to serve requests, but they behave differently on graceful shutdown.
+
+* `bin/rake cf:on_first_instance db:migrate && bin/rails server -p $PORT -e $RAILS_ENV`: The process tree is `bash -> ruby`, so on graceful shutdown only the `bash` process receives the TERM signal, and not the `ruby` process.
+
+* `bin/rake cf:on_first_instance db:migrate && exec bin/rails server -p $PORT -e $RAILS_ENV`: Because of the `exec` prefix on the final command, the `ruby` process invoked by `rails` takes over the `bash` process managing the execution of the composite command. The process tree is only `ruby`, so the ruby web server receives the TERM signal can shutdown gracefully for 10 seconds.
\ No newline at end of file
diff --git a/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/disk_quota.html b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/disk_quota.html
new file mode 100644
index 000000000..f2463dbea
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/disk_quota.html
@@ -0,0 +1,9 @@
+Use the disk_quota attribute to allocate the disk space for your app instance. This attribute requires a unit of measurement: M, MB, G, or GB, in upper case or lower case.
+
+
+---
+ ...
+ disk_quota: 1024M
+
+
+The command line option that overrides this attribute is -k.
diff --git a/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/disk_quota.md b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/disk_quota.md
new file mode 100644
index 000000000..dfd347ccd
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/disk_quota.md
@@ -0,0 +1,9 @@
+Use the `disk_quota` attribute to allocate the disk space for your app instance. This attribute requires a unit of measurement: `M`, `MB`, `G`, or `GB`, in upper case or lower case.
+
+```
+---
+ ...
+ disk_quota: 1024M
+```
+
+The command line option that overrides this attribute is `-k`.
\ No newline at end of file
diff --git a/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/domain.html b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/domain.html
new file mode 100644
index 000000000..8f1af1c01
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/domain.html
@@ -0,0 +1,27 @@
+Every cf push deploys applications to one particular Cloud Foundry instance.
+Every Cloud Foundry instance may have a shared domain set by an admin.
+Unless you specify a domain, Cloud Foundry incorporates that shared domain in the route to your application.
+
+You can use the domain attribute when you want your application to be served from a domain other than the default shared domain.
+
+
+---
+ ...
+ domain: unique-example.com
+
+
+The command line option that overrides this attribute is -d.
+
+The domains attribute
+
+Use the domains attribute to provide multiple domains. If you define both domain and domains attributes, Cloud Foundry creates routes for domains defined in both of these fields.
+
+
+---
+ ...
+ domains:
+ - domain-example1.com
+ - domain-example2.org
+
+
+The command line option that overrides this attribute is -d.
diff --git a/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/domain.md b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/domain.md
new file mode 100644
index 000000000..e25a36620
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/domain.md
@@ -0,0 +1,25 @@
+Every `cf push` deploys applications to one particular Cloud Foundry instance. Every Cloud Foundry instance may have a shared domain set by an admin. Unless you specify a domain, Cloud Foundry incorporates that shared domain in the route to your application.
+
+You can use the `domain` attribute when you want your application to be served from a domain other than the default shared domain.
+
+```
+---
+ ...
+ domain: unique-example.com
+```
+
+The command line option that overrides this attribute is `-d`.
+
+### The domains attribute
+
+Use the `domains` attribute to provide multiple domains. If you define both `domain` and `domains` attributes, Cloud Foundry creates routes for domains defined in both of these fields.
+
+```
+---
+ ...
+ domains:
+ - domain-example1.com
+ - domain-example2.org
+```
+
+The command line option that overrides this attribute is `-d`.
\ No newline at end of file
diff --git a/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/domains.html b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/domains.html
new file mode 100644
index 000000000..0df6ef33b
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/domains.html
@@ -0,0 +1,10 @@
+Use the domains attribute to provide multiple domains. If you define both domain and domains attributes, Cloud Foundry creates routes for domains defined in both of these fields.
+
+---
+ ...
+ domains:
+ - domain-example1.com
+ - domain-example2.org
+
+
+The command line option that overrides this attribute is -d.
diff --git a/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/domains.md b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/domains.md
new file mode 100644
index 000000000..d593178e6
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/domains.md
@@ -0,0 +1,11 @@
+Use the `domains` attribute to provide multiple domains. If you define both `domain` and `domains` attributes, Cloud Foundry creates routes for domains defined in both of these fields.
+
+```
+---
+ ...
+ domains:
+ - domain-example1.com
+ - domain-example2.org
+```
+
+The command line option that overrides this attribute is `-d`.
\ No newline at end of file
diff --git a/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/env.html b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/env.html
new file mode 100644
index 000000000..4c35fe3d7
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/env.html
@@ -0,0 +1,28 @@
+The env block consists of a heading, then one or more environment variable/value pairs.
+
+For example:
+
+
+---
+ ...
+ env:
+ RAILS_ENV: production
+ RACK_ENV: production
+
+
+cf push deploys the application to a container on the server. The variables belong to the container environment.
+
+While the application is running, Cloud Foundry allows you to operate on environment variables.
+
+
+- View all variables:
cf env my-app
+- Set an individual variable:
cf set-env my-app my-variable_name my-variable_value
+- Unset an individual variable:
cf unset-env my-app my-variable_name my-variable_value
+
+
+Environment variables interact with manifests in the following ways:
+
+
+When you deploy an application for the first time, Cloud Foundry reads the variables described in the environment block of the manifest, and adds them to the environment of the container where the application is deployed.
When you stop and then restart an application, its environment variables persist.
diff --git a/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/env.md b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/env.md
new file mode 100644
index 000000000..88bd86d01
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/env.md
@@ -0,0 +1,24 @@
+The `env` block consists of a heading, then one or more environment variable/value pairs.
+
+For example:
+
+```
+---
+ ...
+ env:
+ RAILS_ENV: production
+ RACK_ENV: production
+```
+
+`cf push` deploys the application to a container on the server. The variables belong to the container environment.
+
+While the application is running, Cloud Foundry allows you to operate on environment variables.
+
+* View all variables: `cf env my-app`
+* Set an individual variable: `cf set-env my-app my-variable_name my-variable_value`
+* Unset an individual variable: `cf unset-env my-app my-variable_name my-variable_value`
+
+Environment variables interact with manifests in the following ways:
+
+* When you deploy an application for the first time, Cloud Foundry reads the variables described in the environment block of the manifest, and adds them to the environment of the container where the application is deployed.
+* When you stop and then restart an application, its environment variables persist.
\ No newline at end of file
diff --git a/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/health-check-type.html b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/health-check-type.html
new file mode 100644
index 000000000..30be9affb
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/health-check-type.html
@@ -0,0 +1,9 @@
+Use the health-check-type attribute to set the health_check_type
+flag to either port or none. If you do not provide
+a health-check-type attribute, it defaults to port.
+
+
+---
+ ...
+ health-check-type: none
+
\ No newline at end of file
diff --git a/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/health-check-type.md b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/health-check-type.md
new file mode 100644
index 000000000..fac9be7d7
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/health-check-type.md
@@ -0,0 +1,9 @@
+Use the `health-check-type` attribute to set the `health_check_type`
+flag to either `port` or `none`. If you do not provide a `health-check-type`
+attribute, it defaults to `port`.
+
+```
+---
+ ...
+ health-check-type: none
+```
diff --git a/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/host.html b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/host.html
new file mode 100644
index 000000000..04de4aa7b
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/host.html
@@ -0,0 +1,9 @@
+Use the host attribute to provide a hostname, or subdomain, in the form of a string. This segment of a route helps to ensure that the route is unique. If you do not provide a hostname, the URL for the app takes the form of APP-NAME.DOMAIN.
+
+
+---
+ ...
+ host: my-app
+
+
+The command line option that overrides this attribute is -n.
diff --git a/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/host.md b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/host.md
new file mode 100644
index 000000000..4658d50bf
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/host.md
@@ -0,0 +1,9 @@
+Use the `host` attribute to provide a hostname, or subdomain, in the form of a string. This segment of a route helps to ensure that the route is unique. If you do not provide a hostname, the URL for the app takes the form of `APP-NAME.DOMAIN`.
+
+```
+---
+ ...
+ host: my-app
+```
+
+The command line option that overrides this attribute is `-n`.
diff --git a/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/hosts.html b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/hosts.html
new file mode 100644
index 000000000..de25f32ef
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/hosts.html
@@ -0,0 +1,11 @@
+Use the hosts attribute to provide multiple hostnames, or subdomains. Each hostname generates a unique route for the app. hosts can be used in conjunction with host. If you define both attributes, Cloud Foundry creates routes for hostnames defined in both host and hosts.
+
+
+---
+ ...
+ hosts:
+ - app_host1
+ - app_host2
+
+
+The command line option that overrides this attribute is -n.
diff --git a/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/hosts.md b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/hosts.md
new file mode 100644
index 000000000..9b69c9cf2
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/hosts.md
@@ -0,0 +1,11 @@
+Use the `hosts` attribute to provide multiple hostnames, or subdomains. Each hostname generates a unique route for the app. `hosts` can be used in conjunction with `host`. If you define both attributes, Cloud Foundry creates routes for hostnames defined in both `host` and `hosts`.
+
+```
+---
+ ...
+ hosts:
+ - app_host1
+ - app_host2
+```
+
+The command line option that overrides this attribute is `-n`.
\ No newline at end of file
diff --git a/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/inherit.html b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/inherit.html
new file mode 100644
index 000000000..184350b67
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/inherit.html
@@ -0,0 +1,62 @@
+A single manifest can describe multiple applications. Another powerful technique is to create multiple manifests with inheritance. Here, manifests have parent-child relationships such that children inherit descriptions from a parent. Children can use inherited descriptions as-is, extend them, or override them.
+
+Content in the child manifest overrides content in the parent manifest, if the two conflict.
+
+This technique helps in these and other scenarios:
+
+
+An application has a set of different deployment modes, such as debug, local, and public. Each deployment mode is described in child manifests that extend the settings in a base parent manifest.
An application is packaged with a basic configuration described by a parent manifest. Users can extend the basic configuration by creating child manifests that add new properties or override those in the parent manifest.
+
+The benefits of multiple manifests with inheritance are similar to those of minimizing duplicated content within single manifests. With inheritance, though, we “promote” content by placing it in the parent manifest.
+
+Every child manifest must contain an “inherit” line that points to the parent manifest. Place the inherit line immediately after the three dashes at the top of the child manifest. For example, every child of a parent manifest called base-manifest.yml begins like this:
+
+---
+ ...
+ inherit: base-manifest.yml
+
+
+You do not need to add anything to the parent manifest.
+
+In the simple example below, a parent manifest gives each application minimal resources, while a production child manifest scales them up.
+
+simple-base-manifest.yml
+
+---
+path: .
+domain: shared-domain.com
+memory: 256M
+instances: 1
+services:
+- singular-backend
+
+# app-specific configuration
+applications:
+ - name: springtock
+ host: 765shower
+ path: ./april/build/libs/april-weather.war
+ - name: wintertick
+ host: 321flurry
+ path: ./december/target/december-weather.war
+
+
+simple-prod-manifest.yml
+
+---
+inherit: simple-base-manifest.yml
+applications:
+ - name:springstorm
+ memory: 512M
+ instances: 1
+ host: 765deluge
+ path: ./april/build/libs/april-weather.war
+ - name: winterblast
+ memory: 1G
+ instances: 2
+ host: 321blizzard
+ path: ./december/target/december-weather.war
+
+
+Note: Inheritance can add an additional level of complexity to manifest creation and maintenance. Comments that precisely explain how the child manifest extends or overrides the descriptions in the parent manifest can alleviate this complexity.
\ No newline at end of file
diff --git a/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/inherit.md b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/inherit.md
new file mode 100644
index 000000000..5270dee89
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/inherit.md
@@ -0,0 +1,63 @@
+A single manifest can describe multiple applications. Another powerful technique is to create multiple manifests with inheritance. Here, manifests have parent-child relationships such that children inherit descriptions from a parent. Children can use inherited descriptions as-is, extend them, or override them.
+
+Content in the child manifest overrides content in the parent manifest, if the two conflict.
+
+This technique helps in these and other scenarios:
+
+* An application has a set of different deployment modes, such as debug, local, and public. Each deployment mode is described in child manifests that extend the settings in a base parent manifest.
+
+* An application is packaged with a basic configuration described by a parent manifest. Users can extend the basic configuration by creating child manifests that add new properties or override those in the parent manifest.
+
+The benefits of multiple manifests with inheritance are similar to those of minimizing duplicated content within single manifests. With inheritance, though, we “promote” content by placing it in the parent manifest.
+
+Every child manifest must contain an “inherit” line that points to the parent manifest. Place the inherit line immediately after the three dashes at the top of the child manifest. For example, every child of a parent manifest called `base-manifest.yml` begins like this:
+
+```
+---
+ ...
+ inherit: base-manifest.yml
+```
+You do not need to add anything to the parent manifest.
+
+In the simple example below, a parent manifest gives each application minimal resources, while a production child manifest scales them up.
+
+**simple-base-manifest.yml**
+
+```
+---
+path: .
+domain: shared-domain.com
+memory: 256M
+instances: 1
+services:
+- singular-backend
+
+# app-specific configuration
+applications:
+ - name: springtock
+ host: 765shower
+ path: ./april/build/libs/april-weather.war
+ - name: wintertick
+ host: 321flurry
+ path: ./december/target/december-weather.war
+```
+
+**simple-prod-manifest.yml**
+
+```
+---
+inherit: simple-base-manifest.yml
+applications:
+ - name:springstorm
+ memory: 512M
+ instances: 1
+ host: 765deluge
+ path: ./april/build/libs/april-weather.war
+ - name: winterblast
+ memory: 1G
+ instances: 2
+ host: 321blizzard
+ path: ./december/target/december-weather.war
+```
+
+**Note**: Inheritance can add an additional level of complexity to manifest creation and maintenance. Comments that precisely explain how the child manifest extends or overrides the descriptions in the parent manifest can alleviate this complexity.
\ No newline at end of file
diff --git a/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/instances.html b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/instances.html
new file mode 100644
index 000000000..021991fa5
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/instances.html
@@ -0,0 +1,11 @@
+
Use the instances attribute to specify the number of app instances that you want to start upon push:
+
+
+---
+ ...
+ instances: 2
+
+
+We recommend that you run at least two instances of any apps for which fault tolerance matters.
+
+The command line option that overrides this attribute is -i.
diff --git a/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/instances.md b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/instances.md
new file mode 100644
index 000000000..27bd30d5d
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/instances.md
@@ -0,0 +1,11 @@
+Use the `instances` attribute to specify the number of app instances that you want to start upon push:
+
+```
+---
+ ...
+ instances: 2
+```
+
+We recommend that you run at least two instances of any apps for which fault tolerance matters.
+
+The command line option that overrides this attribute is `-i`.
\ No newline at end of file
diff --git a/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/memory.html b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/memory.html
new file mode 100644
index 000000000..e25ee286e
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/memory.html
@@ -0,0 +1,11 @@
+Use the memory attribute to specify the memory limit for all instances of an app. This attribute requires a unit of measurement: M, MB, G, or GB, in upper case or lower case. For example:
+
+
+---
+ ...
+ memory: 1024M
+
+
+The default memory limit is 1G. You might want to specify a smaller limit to conserve quota space if you know that your app instances do not require 1G of memory.
+
+The command line option that overrides this attribute is -m.
\ No newline at end of file
diff --git a/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/memory.md b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/memory.md
new file mode 100644
index 000000000..3efb02e41
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/memory.md
@@ -0,0 +1,11 @@
+Use the `memory` attribute to specify the memory limit for all instances of an app. This attribute requires a unit of measurement: `M`, `MB`, `G`, or `GB`, in upper case or lower case. For example:
+
+```
+---
+ ...
+ memory: 1024M
+```
+
+The default memory limit is 1G. You might want to specify a smaller limit to conserve quota space if you know that your app instances do not require 1G of memory.
+
+The command line option that overrides this attribute is `-m`.
\ No newline at end of file
diff --git a/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/name.html b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/name.html
new file mode 100644
index 000000000..39d0aac6a
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/name.html
@@ -0,0 +1,10 @@
+The name attribute is the only required attribute
+for an application in a manifest file.
+
+This is an example of a minimal manifest:
+
+
+---
+applications:
+- name: nifty-gui
+
\ No newline at end of file
diff --git a/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/name.md b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/name.md
new file mode 100644
index 000000000..09419ceee
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/name.md
@@ -0,0 +1,9 @@
+The `name` attribute is the only required attribute for an application in a manifest file.
+
+This is an example of a minimal manifest:
+
+```
+---
+applications:
+- name: nifty-gui
+```
\ No newline at end of file
diff --git a/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/no-hostname.html b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/no-hostname.html
new file mode 100644
index 000000000..b3a6047de
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/no-hostname.html
@@ -0,0 +1,9 @@
+By default, if you do not provide a hostname, the URL for the app takes the form of APP-NAME.DOMAIN. If you want to override this and map the root domain to this app then you can set no-hostname as true.
+
+
+---
+ ...
+ no-hostname: true
+
+
+The command line option that corresponds to this attribute is --no-hostname.
diff --git a/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/no-hostname.md b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/no-hostname.md
new file mode 100644
index 000000000..19b73ed31
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/no-hostname.md
@@ -0,0 +1,9 @@
+By default, if you do not provide a hostname, the URL for the app takes the form of `APP-NAME.DOMAIN`. If you want to override this and map the root domain to this app then you can set no-hostname as true.
+
+```
+---
+ ...
+ no-hostname: true
+```
+
+The command line option that corresponds to this attribute is `--no-hostname`.
\ No newline at end of file
diff --git a/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/no-route.html b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/no-route.html
new file mode 100644
index 000000000..d631024fd
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/no-route.html
@@ -0,0 +1,18 @@
+By default, cf push assigns a route to every application. But some applications process data while running in the background, and should not be assigned routes.
+
+You can use the no-route attribute with a value of true to prevent a route from being created for your application.
+
+
+---
+ ...
+ no-route: true
+
+
+The command line option that corresponds to this attribute is --no-route.
+
+If you find that an application which should not have a route does have one:
+
+
+- Remove the route using the
cf unmap-route command.
+- Push the app again with the
no-route: true attribute in the manifest or the --no-route command line option.
+
diff --git a/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/no-route.md b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/no-route.md
new file mode 100644
index 000000000..7cef4e28f
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/no-route.md
@@ -0,0 +1,16 @@
+By default, `cf push` assigns a route to every application. But some applications process data while running in the background, and should not be assigned routes.
+
+You can use the `no-route` attribute with a value of `true` to prevent a route from being created for your application.
+
+```
+---
+ ...
+ no-route: true
+```
+
+The command line option that corresponds to this attribute is `--no-route`.
+
+If you find that an application which should not have a route does have one:
+
+1. Remove the route using the `cf unmap-route` command.
+2. Push the app again with the `no-route: true` attribute in the manifest or the `--no-route` command line option.
\ No newline at end of file
diff --git a/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/path.html b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/path.html
new file mode 100644
index 000000000..a1b1cfb23
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/path.html
@@ -0,0 +1,9 @@
+You can use the path attribute to tell Cloud Foundry where to find your application. This is generally not necessary when you run cf push from the directory where an application is located.
+
+
+---
+ ...
+ path: path_to_application_bits
+
+
+The command line option that overrides this attribute is -p.
diff --git a/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/path.md b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/path.md
new file mode 100644
index 000000000..24d48cb6a
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/path.md
@@ -0,0 +1,9 @@
+You can use the `path` attribute to tell Cloud Foundry where to find your application. This is generally not necessary when you run `cf push` from the directory where an application is located.
+
+```
+---
+ ...
+ path: path_to_application_bits
+```
+
+The command line option that overrides this attribute is `-p`.
\ No newline at end of file
diff --git a/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/random-route.html b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/random-route.html
new file mode 100644
index 000000000..ef432da78
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/random-route.html
@@ -0,0 +1,11 @@
+Use the random-route attribute to create a URL that includes the app name and
+random words.
+Use this attribute to avoid URL collision when pushing the same app to multiple spaces, or to avoid managing app URLs.
+
+The command line option that corresponds to this attribute is --random-route.
+
+
+---
+ ...
+ random-route: true
+
diff --git a/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/random-route.md b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/random-route.md
new file mode 100644
index 000000000..9a7792b77
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/random-route.md
@@ -0,0 +1,9 @@
+Use the `random-route` attribute to create a URL that includes the app name and random words. Use this attribute to avoid URL collision when pushing the same app to multiple spaces, or to avoid managing app URLs.
+
+The command line option that corresponds to this attribute is `--random-route`.
+
+```
+---
+ ...
+ random-route: true
+```
\ No newline at end of file
diff --git a/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/services.html b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/services.html
new file mode 100644
index 000000000..c10713143
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/services.html
@@ -0,0 +1,18 @@
+Applications can bind to services such as databases, messaging, and key-value stores.
+
+Applications are deployed into App Spaces. An application can only bind to services instances that exist in the target App Space before the application is deployed.
+
+The services block consists of a heading, then one or more service instance names.
+
+Whoever creates the service chooses the service instance names. These names can convey logical information, as in backend_queue, describe the nature of the service, as in mysql_5.x, or do neither, as in the example below.
+
+
+---
+ ...
+ services:
+ - instance_ABC
+ - instance_XYZ
+
+
+Binding to a service instance is a special case of setting an environment
+variable, namely VCAP_SERVICES.
diff --git a/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/services.md b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/services.md
new file mode 100644
index 000000000..5fb3e1cb9
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/services.md
@@ -0,0 +1,17 @@
+Applications can bind to services such as databases, messaging, and key-value stores.
+
+Applications are deployed into App Spaces. An application can only bind to services instances that exist in the target App Space before the application is deployed.
+
+The `services` block consists of a heading, then one or more service instance names.
+
+Whoever creates the service chooses the service instance names. These names can convey logical information, as in `backend_queue`, describe the nature of the service, as in `mysql_5.x`, or do neither, as in the example below.
+
+```
+---
+ ...
+ services:
+ - instance_ABC
+ - instance_XYZ
+```
+
+Binding to a service instance is a special case of setting an environment variable, namely `VCAP_SERVICES`.
\ No newline at end of file
diff --git a/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/stack.html b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/stack.html
new file mode 100644
index 000000000..021e2788a
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/stack.html
@@ -0,0 +1,11 @@
+
Use the stack attribute to specify which stack to deploy your application to.
+
+To see a list of available stacks, run cf stacks from the cf cli.
+
+
+---
+ ...
+ stack: cflinuxfs2
+
+
+The command line option that overrides this attribute is -s.
diff --git a/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/stack.md b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/stack.md
new file mode 100644
index 000000000..c46611e1d
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/stack.md
@@ -0,0 +1,11 @@
+Use the `stack` attribute to specify which stack to deploy your application to.
+
+To see a list of available stacks, run `cf stacks` from the cf cli.
+
+```
+---
+ ...
+ stack: cflinuxfs2
+```
+
+The command line option that overrides this attribute is `-s`.
\ No newline at end of file
diff --git a/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/timeout.html b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/timeout.html
new file mode 100644
index 000000000..063e26405
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/timeout.html
@@ -0,0 +1,14 @@
+The timeout attribute defines the number of seconds Cloud Foundry allocates for starting your application.
+
+For example:
+
+
+---
+ ...
+ timeout: 80
+
+
+You can increase the timeout length for very large apps that require more time to start. The default timeout is 60 seconds with an upper bound of 180 seconds.
+Note: Administrators can set the upper bound of the maximum_health_check_timeout property to any value. Any changes to Cloud Controller properties in the deployment manifest require running bosh deploy.
+
+The command line option that overrides the timeout attribute for the shell is -t. Manifest values still apply to applications pushed to the deployment.
diff --git a/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/timeout.md b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/timeout.md
new file mode 100644
index 000000000..bc6f8fa29
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/main/resources/description-by-prop-name/timeout.md
@@ -0,0 +1,15 @@
+The `timeout` attribute defines the number of seconds Cloud Foundry allocates for starting your application.
+
+For example:
+
+```
+---
+ ...
+ timeout: 80
+```
+
+You can increase the timeout length for very large apps that require more time to start. The default timeout is 60 seconds with an upper bound of 180 seconds.
+
+**Note**: Administrators can set the upper bound of the `maximum_health_check_timeout` property to any value. Any changes to Cloud Controller properties in the deployment manifest require running `bosh deploy`.
+
+The command line option that overrides the timeout attribute for the shell is `-t`. Manifest values still apply to applications pushed to the deployment.
\ No newline at end of file
diff --git a/vscode-extensions/vscode-concourse/src/test/java/org/springframework/ide/vscode/manifest/yaml/ManifestYamlEditorTest.java b/vscode-extensions/vscode-concourse/src/test/java/org/springframework/ide/vscode/manifest/yaml/ManifestYamlEditorTest.java
new file mode 100644
index 000000000..9491a37c1
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/test/java/org/springframework/ide/vscode/manifest/yaml/ManifestYamlEditorTest.java
@@ -0,0 +1,492 @@
+/*******************************************************************************
+ * Copyright (c) 2016 Pivotal, Inc.
+ * All rights reserved. This program and the accompanying materials
+ * are made available under the terms of the Eclipse Public License v1.0
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/epl-v10.html
+ *
+ * Contributors:
+ * Pivotal, Inc. - initial API and implementation
+ *******************************************************************************/
+package org.springframework.ide.vscode.manifest.yaml;
+
+import org.junit.Before;
+import org.junit.Test;
+import org.springframework.ide.vscode.languageserver.testharness.Editor;
+import org.springframework.ide.vscode.languageserver.testharness.LanguageServerHarness;
+
+public class ManifestYamlEditorTest {
+
+ LanguageServerHarness harness;
+
+ @Before public void setup() throws Exception {
+ harness = new LanguageServerHarness(ManifestYamlLanguageServer::new);
+ harness.intialize(null);
+ }
+
+ @Test public void testReconcileCatchesParseError() throws Exception {
+
+ Editor editor = harness.newEditor(
+ "somemap: val\n"+
+ "- sequence"
+ );
+ editor.assertProblems(
+ "-|expected "
+ );
+ }
+
+ @Test public void reconcileRunsOnDocumentOpenAndChange() throws Exception {
+ LanguageServerHarness harness = new LanguageServerHarness(ManifestYamlLanguageServer::new);
+ harness.intialize(null);
+
+ Editor editor = harness.newEditor(
+ "somemap: val\n"+
+ "- sequence"
+ );
+
+ editor.assertProblems(
+ "-|expected "
+ );
+
+ editor.setText(
+ "- sequence\n" +
+ "zomemap: val"
+ );
+
+ editor.assertProblems(
+ "z|expected "
+ );
+ }
+
+ @Test
+ public void reconcileMisSpelledPropertyNames() throws Exception {
+ Editor editor;
+
+ editor = harness.newEditor(
+ "memory: 1G\n" +
+ "aplications:\n" +
+ " - buildpack: zbuildpack\n" +
+ " domain: zdomain\n" +
+ " name: foo"
+ );
+ editor.assertProblems("aplications|Unknown property");
+
+ //mispelled or not allowed at toplevel
+ editor = harness.newEditor(
+ "name: foo\n" +
+ "buildpeck: yahah\n" +
+ "memory: 1G\n" +
+ "memori: 1G\n"
+ );
+ editor.assertProblems(
+ "name|Unknown property",
+ "buildpeck|Unknown property",
+ "memori|Unknown property"
+ );
+
+ //mispelled or not allowed as nested
+ editor = harness.newEditor(
+ "applications:\n" +
+ "- name: fine\n" +
+ " buildpeck: yahah\n" +
+ " memory: 1G\n" +
+ " memori: 1G\n" +
+ " applications: bad\n"
+ );
+ editor.assertProblems(
+ "buildpeck|Unknown property",
+ "memori|Unknown property",
+ "applications|Unknown property"
+ );
+ }
+
+ @Test
+ public void reconcileStructuralProblems() throws Exception {
+ Editor editor;
+
+ //forgot the 'applications:' heading
+ editor = harness.newEditor(
+ "- name: foo"
+ );
+ editor.assertProblems(
+ "- name: foo|Expecting a 'Map' but found a 'Sequence'"
+ );
+
+ //forgot to make the '-' after applications
+ editor = harness.newEditor(
+ "applications:\n" +
+ " name: foo"
+ );
+ editor.assertProblems(
+ "name: foo|Expecting a 'Sequence' but found a 'Map'"
+ );
+
+ //Using a 'composite' element where a scalar type is expected
+ editor = harness.newEditor(
+ "memory:\n"+
+ "- bad sequence\n" +
+ "buildpack:\n" +
+ " bad: map\n"
+ );
+ editor.assertProblems(
+ "- bad sequence|Expecting a 'Memory' but found a 'Sequence'",
+ "bad: map|Expecting a 'Buildpack' but found a 'Map'"
+ );
+ }
+
+ @Test
+ public void reconcileSimpleTypes() throws Exception {
+ Editor editor;
+
+ //check for 'format' errors:
+ editor = harness.newEditor(
+ "applications:\n" +
+ "- name: foo\n" +
+ " instances: not a number\n" +
+ " no-route: notBool\n"+
+ " memory: 1024\n" +
+ " disk_quota: 2048\n" +
+ " health-check-type: unhealthy"
+ );
+ editor.assertProblems(
+ "not a number|Positive Integer",
+ "notBool|boolean",
+ "1024|Memory",
+ "2048|Memory",
+ "unhealthy|Health Check Type"
+ );
+
+ //check for 'range' errors:
+ editor = harness.newEditor(
+ "applications:\n" +
+ "- name: foo\n" +
+ " instances: -3\n" +
+ " memory: -1024M\n" +
+ " disk_quota: -2048M\n"
+ );
+ editor.assertProblems(
+ "-3|Positive Integer",
+ "-1024M|Memory",
+ "-2048M|Memory"
+ );
+
+ //check that correct values are indeed accepted
+ editor = harness.newEditor(
+ "applications:\n" +
+ "- name: foo\n" +
+ " instances: 2\n" +
+ " no-route: true\n"+
+ " memory: 1024M\n" +
+ " disk_quota: 2048MB\n"
+ );
+ editor.assertProblems(/*none*/);
+
+ //check that correct values are indeed accepted
+ editor = harness.newEditor(
+ "applications:\n" +
+ "- name: foo\n" +
+ " instances: 2\n" +
+ " no-route: false\n" +
+ " memory: 1024m\n" +
+ " disk_quota: 2048mb\n"
+ );
+ editor.assertProblems(/*none*/);
+
+ editor = harness.newEditor(
+ "applications:\n" +
+ "- name: foo\n" +
+ " instances: 2\n" +
+ " memory: 1G\n" +
+ " disk_quota: 2g\n"
+ );
+ editor.assertProblems(/*none*/);
+ }
+
+ @Test
+ public void noListIndent() throws Exception {
+ Editor editor;
+ editor = harness.newEditor("appl<*>");
+ editor.assertCompletions(
+ "applications:\n"+
+ "- <*>"
+ );
+ }
+
+ @Test
+ public void toplevelCompletions() throws Exception {
+ Editor editor;
+ editor = harness.newEditor("<*>");
+ editor.assertCompletions(
+ "applications:\n"+
+ "- <*>",
+ // ---------------
+ "buildpack: <*>",
+ // ---------------
+ "command: <*>",
+ // ---------------
+ "disk_quota: <*>",
+ // ---------------
+ "domain: <*>",
+ // ---------------
+ "domains:\n"+
+ "- <*>",
+ // ---------------
+ "env:\n"+
+ " <*>",
+ // ---------------
+ "health-check-type: <*>",
+ // ---------------
+// "host: <*>",
+ // ---------------
+// "hosts: \n"+
+// " - <*>",
+ // ---------------
+ "inherit: <*>",
+ // ---------------
+ "instances: <*>",
+ // ---------------
+ "memory: <*>",
+ // ---------------
+// "name: <*>",
+ // ---------------
+ "no-hostname: <*>",
+ // ---------------
+ "no-route: <*>",
+ // ---------------
+ "path: <*>",
+ // ---------------
+ "random-route: <*>",
+ // ---------------
+ "services:\n"+
+ "- <*>",
+ // ---------------
+ "stack: <*>",
+ // ---------------
+ "timeout: <*>"
+ );
+
+ editor = harness.newEditor("ranro<*>");
+ editor.assertCompletions(
+ "random-route: <*>"
+ );
+ }
+
+ @Test
+ public void nestedCompletions() throws Exception {
+ Editor editor;
+ editor = harness.newEditor(
+ "applications:\n" +
+ "- <*>"
+ );
+ editor.assertCompletions(
+ // ---------------
+ "applications:\n" +
+ "- buildpack: <*>",
+ // ---------------
+ "applications:\n" +
+ "- command: <*>",
+ // ---------------
+ "applications:\n" +
+ "- disk_quota: <*>",
+ // ---------------
+ "applications:\n" +
+ "- domain: <*>",
+ // ---------------
+ "applications:\n" +
+ "- domains:\n"+
+ " - <*>",
+ // ---------------
+ "applications:\n" +
+ "- env:\n"+
+ " <*>",
+ // ---------------
+ "applications:\n" +
+ "- health-check-type: <*>",
+ // ---------------
+ "applications:\n" +
+ "- host: <*>",
+ // ---------------
+ "applications:\n" +
+ "- hosts:\n"+
+ " - <*>",
+ // ---------------
+ "applications:\n" +
+ "- instances: <*>",
+ // ---------------
+ "applications:\n" +
+ "- memory: <*>",
+ // ---------------
+ "applications:\n" +
+ "- name: <*>",
+ // ---------------
+ "applications:\n" +
+ "- no-hostname: <*>",
+ // ---------------
+ "applications:\n" +
+ "- no-route: <*>",
+ // ---------------
+ "applications:\n" +
+ "- path: <*>",
+ // ---------------
+ "applications:\n" +
+ "- random-route: <*>",
+ // ---------------
+ "applications:\n" +
+ "- services:\n"+
+ " - <*>",
+ // ---------------
+ "applications:\n" +
+ "- stack: <*>",
+ // ---------------
+ "applications:\n" +
+ "- timeout: <*>"
+ );
+ }
+
+ @Test
+ public void completionDetailsAndDocs() throws Exception {
+ Editor editor = harness.newEditor(
+ "applications:\n" +
+ "- build<*>"
+ );
+ editor.assertCompletionDetails("buildpack", "Buildpack", "If your application requires a custom buildpack");
+ }
+
+ @Test
+ public void valueCompletions() throws Exception {
+ assertCompletions("disk_quota: <*>",
+ "disk_quota: 1024M<*>",
+ "disk_quota: 256M<*>",
+ "disk_quota: 512M<*>"
+ );
+ assertCompletions("memory: <*>",
+ "memory: 1024M<*>",
+ "memory: 256M<*>",
+ "memory: 512M<*>"
+ );
+ assertCompletions("no-hostname: <*>",
+ "no-hostname: false<*>",
+ "no-hostname: true<*>"
+ );
+ assertCompletions("no-route: <*>",
+ "no-route: false<*>",
+ "no-route: true<*>"
+ );
+ assertCompletions("random-route: <*>",
+ "random-route: false<*>",
+ "random-route: true<*>"
+ );
+
+ assertCompletions("health-check-type: <*>",
+ "health-check-type: none<*>",
+ "health-check-type: port<*>"
+ );
+ }
+
+ @Test
+ public void hoverInfos() throws Exception {
+ Editor editor = harness.newEditor(
+ "memory: 1G\n" +
+ "#comment\n" +
+ "inherit: base-manifest.yml\n"+
+ "applications:\n" +
+ "- buildpack: zbuildpack\n" +
+ " domain: zdomain\n" +
+ " name: foo\n" +
+ " command: java main.java\n" +
+ " disk_quota: 1024M\n" +
+ " domains:\n" +
+ " - pivotal.io\n" +
+ " - otherdomain.org\n" +
+ " env:\n" +
+ " RAILS_ENV: production\n" +
+ " RACK_ENV: production\n" +
+ " host: apppage\n" +
+ " hosts:\n" +
+ " - apppage2\n" +
+ " - appage3\n" +
+ " instances: 2\n" +
+ " no-hostname: true\n" +
+ " no-route: true\n" +
+ " path: somepath/app.jar\n" +
+ " random-route: true\n" +
+ " services:\n" +
+ " - instance_ABC\n" +
+ " - instance_XYZ\n" +
+ " stack: cflinuxfs2\n" +
+ " timeout: 80\n" +
+ " health-check-type: none\n"
+ );
+
+ editor.assertIsHoverRegion("memory");
+ editor.assertIsHoverRegion("inherit");
+ editor.assertIsHoverRegion("applications");
+ editor.assertIsHoverRegion("buildpack");
+ editor.assertIsHoverRegion("domain");
+ editor.assertIsHoverRegion("name");
+ editor.assertIsHoverRegion("command");
+ editor.assertIsHoverRegion("disk_quota");
+ editor.assertIsHoverRegion("domains");
+ editor.assertIsHoverRegion("env");
+ editor.assertIsHoverRegion("host");
+ editor.assertIsHoverRegion("hosts");
+ editor.assertIsHoverRegion("instances");
+ editor.assertIsHoverRegion("no-hostname");
+ editor.assertIsHoverRegion("no-route");
+ editor.assertIsHoverRegion("path");
+ editor.assertIsHoverRegion("random-route");
+ editor.assertIsHoverRegion("services");
+ editor.assertIsHoverRegion("stack");
+ editor.assertIsHoverRegion("timeout");
+ editor.assertIsHoverRegion("health-check-type");
+
+ editor.assertHoverContains("memory", "Use the `memory` attribute to specify the memory limit");
+ editor.assertHoverContains("1G", "Use the `memory` attribute to specify the memory limit");
+ editor.assertHoverContains("inherit", "For example, every child of a parent manifest called `base-manifest.yml` begins like this");
+ editor.assertHoverContains("buildpack", "use the `buildpack` attribute to specify its URL or name");
+ editor.assertHoverContains("name", "The `name` attribute is the only required attribute for an application in a manifest file");
+ editor.assertHoverContains("command", "On the command line, use the `-c` option to specify the custom start command as the following example shows");
+ editor.assertHoverContains("disk_quota", "Use the `disk_quota` attribute to allocate the disk space for your app instance");
+ editor.assertHoverContains("domain", "You can use the `domain` attribute when you want your application to be served");
+ editor.assertHoverContains("domains", "Use the `domains` attribute to provide multiple domains");
+ editor.assertHoverContains("env", "The `env` block consists of a heading, then one or more environment variable/value pairs");
+ editor.assertHoverContains("host", "Use the `host` attribute to provide a hostname, or subdomain, in the form of a string");
+ editor.assertHoverContains("hosts", "Use the `hosts` attribute to provide multiple hostnames, or subdomains");
+ editor.assertHoverContains("instances", "Use the `instances` attribute to specify the number of app instances that you want to start upon push");
+ editor.assertHoverContains("no-hostname", "By default, if you do not provide a hostname, the URL for the app takes the form of `APP-NAME.DOMAIN`");
+ editor.assertHoverContains("no-route", "You can use the `no-route` attribute with a value of `true` to prevent a route from being created for your application");
+ editor.assertHoverContains("path", "You can use the `path` attribute to tell Cloud Foundry where to find your application");
+ editor.assertHoverContains("random-route", "Use the `random-route` attribute to create a URL that includes the app name and random words");
+ editor.assertHoverContains("services", "The `services` block consists of a heading, then one or more service instance names");
+ editor.assertHoverContains("stack", "Use the `stack` attribute to specify which stack to deploy your application to.");
+ editor.assertHoverContains("timeout", "The `timeout` attribute defines the number of seconds Cloud Foundry allocates for starting your application");
+ editor.assertHoverContains("health-check-type", "Use the `health-check-type` attribute to");
+ }
+
+ @Test
+ public void noHoverInfos() throws Exception {
+ Editor editor = harness.newEditor(
+ "#comment\n" +
+ "applications:\n" +
+ "- buildpack: zbuildpack\n" +
+ " name: foo\n" +
+ " domains:\n" +
+ " - pivotal.io\n" +
+ " - otherdomain.org\n"
+
+ );
+ editor.assertNoHover("comment");
+
+ // May fail in the future if hover support is added, but if hover support is added in the future,
+ // it is expected that these should start to fail, as right now they have no hover
+ editor.assertNoHover("pivotal.io");
+ editor.assertNoHover("otherdomain.org");
+ }
+
+ //////////////////////////////////////////////////////////////////////////////
+
+ private void assertCompletions(String textBefore, String... textAfter) throws Exception {
+ Editor editor = harness.newEditor(textBefore);
+ editor.assertCompletions(textAfter);
+ }
+}
diff --git a/vscode-extensions/vscode-concourse/src/test/java/org/springframework/ide/vscode/manifest/yaml/ManifestYamlLanguageServerTest.java b/vscode-extensions/vscode-concourse/src/test/java/org/springframework/ide/vscode/manifest/yaml/ManifestYamlLanguageServerTest.java
new file mode 100644
index 000000000..7d9d3aeb7
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/test/java/org/springframework/ide/vscode/manifest/yaml/ManifestYamlLanguageServerTest.java
@@ -0,0 +1,67 @@
+package org.springframework.ide.vscode.manifest.yaml;
+
+import static org.assertj.core.api.Assertions.assertThat;
+
+import java.io.File;
+import java.net.URISyntaxException;
+import java.nio.file.Paths;
+
+import org.eclipse.lsp4j.InitializeResult;
+import org.eclipse.lsp4j.TextDocumentSyncKind;
+import org.junit.Test;
+import org.springframework.ide.vscode.languageserver.testharness.LanguageServerHarness;
+
+public class ManifestYamlLanguageServerTest {
+
+ public static File getTestResource(String name) throws URISyntaxException {
+ return Paths.get(ManifestYamlLanguageServerTest.class.getResource(name).toURI()).toFile();
+ }
+
+ @Test
+ public void createAndInitializeServerWithWorkspace() throws Exception {
+ LanguageServerHarness harness = new LanguageServerHarness(ManifestYamlLanguageServer::new);
+ File workspaceRoot = getTestResource("/workspace/");
+ assertExpectedInitResult(harness.intialize(workspaceRoot));
+ }
+
+ @Test
+ public void createAndInitializeServerWithoutWorkspace() throws Exception {
+ File workspaceRoot = null;
+ LanguageServerHarness harness = new LanguageServerHarness(ManifestYamlLanguageServer::new);
+ assertExpectedInitResult(harness.intialize(workspaceRoot));
+ }
+
+// @Test public void completions() throws Exception {
+// LanguageServerHarness harness = new LanguageServerHarness(ManifestYamlLanguageServer::new);
+//
+// File workspaceRoot = getTestResource("/workspace/");
+// assertExpectedInitResult(harness.intialize(workspaceRoot));
+//
+// TextDocumentInfo doc = harness.openDocument(getTestResource("/workspace/testfile.yml"));
+//
+// CompletionList completions = harness.getCompletions(doc, doc.positionOf("foo"));
+// assertThat(completions.isIncomplete()).isFalse();
+// assertThat(completions.getItems())
+// .extracting(CompletionItem::getLabel)
+// .containsExactly("TypeScript", "JavaScript");
+//
+// List resolved = harness.resolveCompletions(completions);
+// assertThat(resolved)
+// .extracting(CompletionItem::getLabel)
+// .containsExactly("TypeScript", "JavaScript");
+//
+// assertThat(resolved)
+// .extracting(CompletionItem::getDetail)
+// .containsExactly("TypeScript details", "JavaScript details");
+//
+// assertThat(resolved)
+// .extracting(CompletionItem::getDocumentation)
+// .containsExactly("TypeScript docs", "JavaScript docs");
+// }
+
+ private void assertExpectedInitResult(InitializeResult initResult) {
+ assertThat(initResult.getCapabilities().getCompletionProvider().getResolveProvider()).isFalse();
+ assertThat(initResult.getCapabilities().getTextDocumentSync()).isEqualTo(TextDocumentSyncKind.Incremental);
+ }
+
+}
diff --git a/vscode-extensions/vscode-concourse/src/test/java/org/springframework/ide/vscode/manifest/yaml/ManifestYmlSchemaTest.java b/vscode-extensions/vscode-concourse/src/test/java/org/springframework/ide/vscode/manifest/yaml/ManifestYmlSchemaTest.java
new file mode 100644
index 000000000..02a5f4727
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/test/java/org/springframework/ide/vscode/manifest/yaml/ManifestYmlSchemaTest.java
@@ -0,0 +1,155 @@
+package org.springframework.ide.vscode.manifest.yaml;
+/*******************************************************************************
+ * Copyright (c) 2015, 2016 Pivotal, Inc.
+ * All rights reserved. This program and the accompanying materials
+ * are made available under the terms of the Eclipse Public License v1.0
+ * which accompanies this distribution, and is available at
+ * http://www.eclipse.org/legal/epl-v10.html
+ *
+ * Contributors:
+ * Pivotal, Inc. - initial API and implementation
+ *******************************************************************************/
+
+
+import static org.junit.Assert.assertEquals;
+import static org.junit.Assert.assertFalse;
+import static org.junit.Assert.assertTrue;
+
+import java.util.List;
+import java.util.Map;
+
+import org.junit.Test;
+import org.springframework.ide.vscode.commons.util.Renderables;
+import org.springframework.ide.vscode.commons.util.StringUtil;
+import org.springframework.ide.vscode.commons.yaml.schema.YTypedProperty;
+import org.springframework.ide.vscode.commons.yaml.schema.YTypeFactory.YBeanType;
+import org.springframework.ide.vscode.commons.yaml.schema.YTypeFactory.YSeqType;
+import org.springframework.ide.vscode.manifest.yaml.ManifestYmlSchema;
+
+import com.google.common.collect.ImmutableSet;
+import com.google.common.collect.ImmutableSet.Builder;
+
+/**
+ * @author Kris De Volder
+ */
+public class ManifestYmlSchemaTest {
+
+ private static final String[] NESTED_PROP_NAMES = {
+// "applications",
+ "buildpack",
+ "command",
+ "disk_quota",
+ "domain",
+ "domains",
+ "env",
+ "health-check-type",
+ "host",
+ "hosts",
+// "inherit",
+ "instances",
+ "memory",
+ "name",
+ "no-hostname",
+ "no-route",
+ "path",
+ "random-route",
+ "services",
+ "stack",
+ "timeout"
+ };
+
+ private static final String[] TOPLEVEL_PROP_NAMES = {
+ "applications",
+ "buildpack",
+ "command",
+ "disk_quota",
+ "domain",
+ "domains",
+ "env",
+ "health-check-type",
+// "host",
+// "hosts",
+ "inherit",
+ "instances",
+ "memory",
+// "name",
+ "no-hostname",
+ "no-route",
+ "path",
+ "random-route",
+ "services",
+ "stack",
+ "timeout"
+ };
+
+ ManifestYmlSchema schema = new ManifestYmlSchema(null);
+
+ @Test
+ public void toplevelProperties() throws Exception {
+ assertPropNames(schema.getTopLevelType().getProperties(), TOPLEVEL_PROP_NAMES);
+ assertPropNames(schema.getTopLevelType().getPropertiesMap(), TOPLEVEL_PROP_NAMES);
+ }
+
+ @Test
+ public void nestedProperties() throws Exception {
+ assertPropNames(getNestedProps(), NESTED_PROP_NAMES);
+ }
+
+ @Test
+ public void toplevelPropertiesHaveDescriptions() {
+ for (YTypedProperty p : schema.getTopLevelType().getProperties()) {
+ if (!p.getName().equals("applications")) {
+ assertHasRealDescription(p);
+ }
+ }
+ }
+
+ @Test
+ public void nestedPropertiesHaveDescriptions() {
+ for (YTypedProperty p : getNestedProps()) {
+ assertHasRealDescription(p);
+ }
+ }
+
+ //////////////////////////////////////////////////////////////////////////////
+
+ private void assertHasRealDescription(YTypedProperty p) {
+ {
+ String noDescriptionText = Renderables.NO_DESCRIPTION.toHtml();
+ String actual = p.getDescription().toHtml();
+ String msg = "Description missing for '"+p.getName()+"'";
+ assertTrue(msg, StringUtil.hasText(actual));
+ assertFalse(msg, noDescriptionText.equals(actual));
+ }
+ {
+ String noDescriptionText = Renderables.NO_DESCRIPTION.toMarkdown();
+ String actual = p.getDescription().toMarkdown();
+ String msg = "Description missing for '"+p.getName()+"'";
+ assertTrue(msg, StringUtil.hasText(actual));
+ assertFalse(msg, noDescriptionText.equals(actual));
+ }
+ }
+
+ private List getNestedProps() {
+ YSeqType applications = (YSeqType) schema.getTopLevelType().getPropertiesMap().get("applications").getType();
+ YBeanType application = (YBeanType) applications.getDomainType();
+ return application.getProperties();
+ }
+
+ private void assertPropNames(List properties, String... expectedNames) {
+ assertEquals(ImmutableSet.copyOf(expectedNames), getNames(properties));
+ }
+
+ private void assertPropNames(Map propertiesMap, String[] toplevelPropNames) {
+ assertEquals(ImmutableSet.copyOf(toplevelPropNames), ImmutableSet.copyOf(propertiesMap.keySet()));
+ }
+
+ private ImmutableSet getNames(Iterable properties) {
+ Builder builder = ImmutableSet.builder();
+ for (YTypedProperty p : properties) {
+ builder.add(p.getName());
+ }
+ return builder.build();
+ }
+
+}
diff --git a/vscode-extensions/vscode-concourse/src/test/resources/workspace/manifest.yml b/vscode-extensions/vscode-concourse/src/test/resources/workspace/manifest.yml
new file mode 100644
index 000000000..7160866ac
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/src/test/resources/workspace/manifest.yml
@@ -0,0 +1,5 @@
+#Comment
+applications:
+- name: foo
+ buildpack: something
+
\ No newline at end of file
diff --git a/vscode-extensions/vscode-concourse/test/examples/destroy-pipeline.sh b/vscode-extensions/vscode-concourse/test/examples/destroy-pipeline.sh
new file mode 100755
index 000000000..09a9e09db
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/test/examples/destroy-pipeline.sh
@@ -0,0 +1,4 @@
+#!/bin/bash
+branch=`git rev-parse --abbrev-ref HEAD`
+fly -t tools destroy-pipeline -p sts4-${branch}
+
diff --git a/vscode-extensions/vscode-concourse/test/examples/docker/Dockerfile b/vscode-extensions/vscode-concourse/test/examples/docker/Dockerfile
new file mode 100644
index 000000000..02f4a5a1f
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/test/examples/docker/Dockerfile
@@ -0,0 +1,17 @@
+FROM ubuntu:16.04
+
+ADD npmrc /root/.npmrc
+
+RUN apt-get update && apt-get install -y \
+ build-essential \
+ gettext-base \
+ git \
+ jq \
+ openjdk-8-jdk \
+ maven \
+ curl
+
+RUN curl -sL https://deb.nodesource.com/setup_6.x | bash - \
+ && apt-get install -y nodejs
+
+CMD /bin/bash
diff --git a/vscode-extensions/vscode-concourse/test/examples/docker/npmrc b/vscode-extensions/vscode-concourse/test/examples/docker/npmrc
new file mode 100644
index 000000000..3364a1762
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/test/examples/docker/npmrc
@@ -0,0 +1 @@
+unsafe-perm=true
\ No newline at end of file
diff --git a/vscode-extensions/vscode-concourse/test/examples/pipeline.yml b/vscode-extensions/vscode-concourse/test/examples/pipeline.yml
new file mode 100644
index 000000000..243fb8854
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/test/examples/pipeline.yml
@@ -0,0 +1,116 @@
+##########################################################
+resource_types:
+- name: s3-multi
+ type: docker-image
+ source:
+ repository: kdvolder/s3-resource-simple
+- name: slack-notification
+ type: docker-image
+ source:
+ repository: cfcommunity/slack-notification-resource
+ tag: latest
+#########################################################
+resources:
+- name: docker-git
+ type: git
+ source:
+ uri: git@github.com:spring-projects/sts4.git
+ branch: {{branch}}
+ username: kdvolder
+ private_key: {{rsa_id}}
+ paths:
+ - concourse/docker
+- name: sts4
+ type: git
+ source:
+ uri: git@github.com:spring-projects/sts4.git
+ branch: {{branch}}
+ private_key: {{rsa_id}}
+- name: s3-boot-properties-vsix
+ type: s3
+ source:
+ bucket: {{s3_bucket}}
+ access_key_id: {{s3_accesskey}}
+ secret_access_key: {{s3_secretkey}}
+ region_name: {{s3_region}}
+ regexp: sts4/vscode-extensions/vscode-boot-properties-(.*).vsix
+- name: s3-manifest-yaml-vsix
+ type: s3
+ source:
+ bucket: {{s3_bucket}}
+ access_key_id: {{s3_accesskey}}
+ secret_access_key: {{s3_secretkey}}
+ region_name: {{s3_region}}
+ regexp: sts4/vscode-extensions/vscode-manifest-yaml-(.*).vsix
+- name: website
+ type: s3-multi
+ source:
+ bucket: {{s3_prod_bucket}}
+ access_key_id: {{s3_prod_accesskey}}
+ secret_access_key: {{s3_prod_secretkey}}
+ region_name: {{s3_region}}
+ path: snapshot/STS4/vscode-extensions
+ options:
+ - "--acl public-read"
+- name: slack-notification
+ type: slack-notification
+ source:
+ url: https://hooks.slack.com/services/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
+- name: docker-image
+ type: docker-image
+ source:
+ username: {{docker_hub_username}}
+ email: {{docker_hub_email}}
+ password: {{docker_hub_password}}
+ repository: kdvolder/sts4-build-env
+########################################################################################
+jobs:
+- name: build-docker-image
+ serial: true
+ plan:
+ - get: docker-git
+ trigger: true
+ - put: docker-image
+ params:
+ build: docker-git/concourse/docker
+ get_params:
+ skip_download: true
+- name: build-vsix
+ plan:
+ - get: sts4
+ trigger: true
+ - task: build-vscode-extensions
+ file: sts4/concourse/tasks/build-vscode-extensions.yml
+ on_success:
+ aggregate:
+ - put: s3-manifest-yaml-vsix
+ params:
+ file: vsix-files/vscode-manifest-yaml-*.vsix
+ acl: public-read
+ - put: s3-boot-properties-vsix
+ params:
+ file: vsix-files/vscode-boot-properties-*.vsix
+ acl: public-read
+ on_failure:
+ put: slack-notification
+ params:
+ channel: "@kdvolder"
+ text: |
+ Concourse ${BUILD_PIPELINE_NAME}/${BUILD_JOB_NAME}/${BUILD_NAME} has failed!
+- name: build-website
+ plan:
+ - aggregate:
+ - get: sts4
+ - get: s3-manifest-yaml-vsix
+ passed:
+ - build-vsix
+ trigger: true
+ - get: s3-boot-properties-vsix
+ passed:
+ - build-vsix
+ trigger: true
+ - task: build-website
+ file: sts4/concourse/tasks/build-website.yml
+ - put: website
+ params:
+ path: website
diff --git a/vscode-extensions/vscode-concourse/test/examples/set-pipeline.sh b/vscode-extensions/vscode-concourse/test/examples/set-pipeline.sh
new file mode 100755
index 000000000..2fcdaabc5
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/test/examples/set-pipeline.sh
@@ -0,0 +1,3 @@
+#!/bin/bash
+branch=`git rev-parse --abbrev-ref HEAD`
+fly -t tools set-pipeline --var "branch=${branch}" --load-vars-from ${HOME}/.sts4-concourse-credentials.yml -p sts4-${branch} -c pipeline.yml
diff --git a/vscode-extensions/vscode-concourse/test/examples/tasks/build-stuff.yml b/vscode-extensions/vscode-concourse/test/examples/tasks/build-stuff.yml
new file mode 100644
index 000000000..e69de29bb
diff --git a/vscode-extensions/vscode-concourse/test/examples/tasks/build-vscode-extensions.sh b/vscode-extensions/vscode-concourse/test/examples/tasks/build-vscode-extensions.sh
new file mode 100755
index 000000000..c18fdfb05
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/test/examples/tasks/build-vscode-extensions.sh
@@ -0,0 +1,10 @@
+#!/bin/bash
+set -e
+workdir=`pwd`
+
+cd sts4/vscode-extensions
+./build-all.sh
+
+cd $workdir
+cp `find sts4/vscode-extensions -name "*.vsix"` vsix-files
+
diff --git a/vscode-extensions/vscode-concourse/test/examples/tasks/build-vscode-extensions.yml b/vscode-extensions/vscode-concourse/test/examples/tasks/build-vscode-extensions.yml
new file mode 100644
index 000000000..11a108490
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/test/examples/tasks/build-vscode-extensions.yml
@@ -0,0 +1,11 @@
+inputs:
+- name: sts4
+outputs:
+- name: vsix-files
+platform: linux
+image_resource:
+ type: docker-image
+ source:
+ repository: kdvolder/sts4-build-env
+run:
+ path: "sts4/concourse/tasks/build-vscode-extensions.sh"
diff --git a/vscode-extensions/vscode-concourse/test/examples/tasks/build-website.sh b/vscode-extensions/vscode-concourse/test/examples/tasks/build-website.sh
new file mode 100755
index 000000000..50ec31994
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/test/examples/tasks/build-website.sh
@@ -0,0 +1,43 @@
+#!/bin/bash
+set -e
+workdir=`pwd`
+sources=$workdir/sts4/eclipse-distribution/common/html
+target=$workdir/website
+
+#cp -r "${sources}/stylesheet.css" "$target"
+#cp -r ${sources}/*.js "$target"
+#cp s3-manifest-yaml-vsix/*.vsix "$target"
+#cp s3-boot-properties-vsix/*.vsix "$target"
+
+export vscode_manifest_yaml=$(basename s3-manifest-yaml-vsix/*.vsix)
+echo "vscode_manifest_yaml=$vscode_manifest_yaml"
+export vscode_boot_properties=$(basename s3-boot-properties-vsix/*.vsix)
+echo "vscode_boot_properties=$vscode_boot_properties"
+
+envsubst > "$target/vscode-extensions-snippet.html" << XXXXXX
+
+XXXXXX
+
+export vscode_snippet=`cat "$target/vscode-extensions-snippet.html"`
+
+envsubst > "$target/vscode-extensions.html" << XXXXXX
+
+
+
+
+STS4 Vscode Extensions
+
+$vscode_snippet
+
+
+
+XXXXXX
+
+cat $target/vscode-extensions.html
diff --git a/vscode-extensions/vscode-concourse/test/examples/tasks/build-website.yml b/vscode-extensions/vscode-concourse/test/examples/tasks/build-website.yml
new file mode 100644
index 000000000..c6325f3e7
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/test/examples/tasks/build-website.yml
@@ -0,0 +1,13 @@
+inputs:
+- name: sts4
+- name: s3-manifest-yaml-vsix
+- name: s3-boot-properties-vsix
+outputs:
+- name: website
+platform: linux
+image_resource:
+ type: docker-image
+ source:
+ repository: kdvolder/sts4-build-env
+run:
+ path: "sts4/concourse/tasks/build-website.sh"
diff --git a/vscode-extensions/vscode-concourse/test/examples/tasks/test-stuff.yml b/vscode-extensions/vscode-concourse/test/examples/tasks/test-stuff.yml
new file mode 100644
index 000000000..e69de29bb
diff --git a/vscode-extensions/vscode-concourse/tsconfig.json b/vscode-extensions/vscode-concourse/tsconfig.json
new file mode 100644
index 000000000..1905ffea7
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/tsconfig.json
@@ -0,0 +1,21 @@
+{
+ "compilerOptions": {
+ "module": "commonjs",
+ "moduleResolution": "node",
+ "target": "es6",
+ "lib": [
+ "es6"
+ ],
+ "declaration": true,
+ "outDir": "out",
+ "sourceMap": true,
+ "rootDir": "."
+ },
+ "include": [
+ "typings/*.d.ts",
+ "lib/**/*.ts"
+ ],
+ "exclude": [
+ "node_modules"
+ ]
+}
\ No newline at end of file
diff --git a/vscode-extensions/vscode-concourse/tsd.json b/vscode-extensions/vscode-concourse/tsd.json
new file mode 100644
index 000000000..50cd71dcf
--- /dev/null
+++ b/vscode-extensions/vscode-concourse/tsd.json
@@ -0,0 +1,12 @@
+{
+ "version": "v4",
+ "repo": "borisyankov/DefinitelyTyped",
+ "ref": "master",
+ "path": "typings",
+ "bundle": "typings/tsd.d.ts",
+ "installed": {
+ "node/node.d.ts": {
+ "commit": "d22516f9f089de107d7e7d5938566377370631f6"
+ }
+ }
+}