Store certification docs (#6501)

docker-store/certify-images.md

@@ -158,7 +158,7 @@ There are three steps: (1) install git, (2) configure credentials, and (3) confi
     chmod u+x inspectDockerImage
     ```
 
-3.  Capture the product ID (from the URL in Docker Store) that you want to reference for the certification test.
+3.  Get the product ID from the plan page you'd like to reference for the certification test. Make sure the checkbox is checked and the plan is saved first.
 
     ![product ID](images/store-product-id.png)
 
@@ -244,10 +244,10 @@ docker container run -d \
 $1
   ```
 
-#### To inspect the Docker image, `gforghetti/tomcat-wildbook:latest`, with a custom startup script:
+#### To inspect the Docker image, `gforghetti/tomcat-wildbook:latest`, with a custom startup script and upload the result to Docker Store (leave out the `-product-id` parameter if you are just testing):
 
 ```
-root:[~/] # ./inspectDockerimage --start-script ./run_my_application.sh gforghetti/tomcat-wildbook:latest
+root:[~/] # ./inspectDockerimage --start-script ./run_my_application.sh -product-id=<store-product-id> gforghetti/tomcat-wildbook:latest
 ```
 
 #### Output:
@@ -454,6 +454,12 @@ Passed:  This test was performed on Docker Enterprise Edition.
 
 The inspection of the Docker image gforghetti/tomcat-wildbook:latest has completed.
 
+If -product-id is specified on command line:
+**************************************************************************************************************************************************************************************************
+* Step #16 Upload the test result to Docker Store.
+**************************************************************************************************************************************************************************************************
+Passed:   The test results are uploaded to Docker Store.
+
 root:[~/] #
 ```
 

docker-store/certify-plugins-logging.md

@@ -44,11 +44,6 @@ The custom script must log the contents of the `quotes.txt` file. It should also
 
 Best practices require Docker logging plugins to support the [ReadLogs API](/engine/extend/plugins_logging/#logdriverreadlogs) so that the logs can be retrieved with the `docker container logs` command. If the `ReadLogs` API is not supported, a custom script is needed to retrieve the logs and print them to `stdout`. Refer to the `--get-logs-script` command argument in the command help.
 
-
-### External server
-
-To send data to an external server, use the [http_api_endpoint](#http_api_endpoint) HTTP Server for your docker logging plugin. You can run the [http_api_endpoint](#http_api_endpoint) HTTP Server and have the docker logging plugin send its logging data to the [http_api_endpoint](http_api_endpoint/README.md) HTTP Server. The data can then be retrieved using a `curl` command. Refer to the [http_api_endpoint](#http_api_endpoint) HTTP Server for more details.
-
 ### Prerequisites
 
 Your Docker EE installation must be running on the server used to verify your submissions. If necessary, request entitlement to a specific [Docker Enterprise Edition](https://store.docker.com/editions/enterprise/docker-ee-trial).
@@ -158,12 +153,10 @@ There are three steps: (1) install git, (2) configure credentials, and (3) confi
 
     | OS/Architecture | Download Link |
     |-----------------|------------------|
-    | Windows/X86  | https://s3.amazonaws.com/store-logos-us-east-1/certification/windows/inspectDockerLoggingPlugin.exe |
-    | Windows/X86 | https://s3.amazonaws.com/store-logos-us-east-1/certification/windows/http_api_endpoint.exe |
-    | Linux/X86 | https://s3.amazonaws.com/store-logos-us-east-1/certification/linux/inspectDockerLoggingPlugin |
-    | Linux/X86 | https://s3.amazonaws.com/store-logos-us-east-1/certification/linux/http_api_endpoint |
-    | Linux/IBMZ | https://s3.amazonaws.com/store-logos-us-east-1/certification/zlinux/inspectDockerLoggingPlugin |
-    | Linux/IBMPOWER | https://s3.amazonaws.com/store-logos-us-east-1/certification/power/inspectDockerLoggingPlugin |
+    | Windows/X86  | [https://s3.amazonaws.com/store-logos-us-east-1/certification/windows/inspectDockerLoggingPlugin.exe](https://s3.amazonaws.com/store-logos-us-east-1/certification/windows/inspectDockerLoggingPlugin.exe) |
+    | Linux/X86 | [https://s3.amazonaws.com/store-logos-us-east-1/certification/linux/inspectDockerLoggingPlugin](https://s3.amazonaws.com/store-logos-us-east-1/certification/linux/inspectDockerLoggingPlugin) |
+    | Linux/IBMZ | [https://s3.amazonaws.com/store-logos-us-east-1/certification/zlinux/inspectDockerLoggingPlugin](https://s3.amazonaws.com/store-logos-us-east-1/certification/zlinux/inspectDockerLoggingPlugin) |
+    | Linux/IBMPOWER | [https://s3.amazonaws.com/store-logos-us-east-1/certification/power/inspectDockerLoggingPlugin](https://s3.amazonaws.com/store-logos-us-east-1/certification/power/inspectDockerLoggingPlugin) |
 
 2.  Set permissions on `inspectDockerLoggingPlugin` so that it is executable:
 
@@ -171,7 +164,7 @@ There are three steps: (1) install git, (2) configure credentials, and (3) confi
     chmod u+x inspectDockerLoggingPlugin
     ```
 
-3.  Capture the product ID you'd like to reference for the certification test.
+3.  Get the product ID from the plan page you'd like to reference for the certification test. Make sure the checkbox is checked and the plan is saved first.
 
     ![product ID](images/store-product-id.png)
 
@@ -231,10 +224,10 @@ By default, `inspectDockerLoggingPlugin` displays output locally to `stdout` (th
 
 ### Inspect a Docker logging plugin with messages sent to stdout
 
-#### To inspect the Docker logging plugin "gforghetti/docker-log-driver-test:latest":
+#### To inspect the Docker logging plugin "gforghetti/docker-log-driver-test:latest", and upload the result to Docker Store (leave out the `-product-id` parameter if you are just testing):
 
 ```
-gforghetti:~:$ ./inspectDockerLoggingPlugin gforghetti/docker-log-driver-test:latest
+gforghetti:~:$ ./inspectDockerLoggingPlugin -product-id=<store-product-id> gforghetti/docker-log-driver-test:latest
 ```
 #### Output:
 
@@ -318,6 +311,13 @@ Passed:   Docker container and any associated volumes removed.
 Passed:   Docker logging plugin gforghetti/docker-log-driver-test:latest was removed.
 
 The inspection of the Docker logging plugin gforghetti/docker-log-driver-test:latest has completed.
+
+If -product-id is specified on command line:
+**************************************************************************************************************************************************************************************************
+* Step #10 Upload the test result to Docker Store.
+**************************************************************************************************************************************************************************************************
+Passed:   The test results are uploaded to Docker Store.
+
 gforghetti:~/$
 ```
 
@@ -416,6 +416,11 @@ The [Sumo Logic Logging Plugin](https://store.docker.com/plugins/sumologic-loggi
 
 You can configure those docker logging plugins to send their logging data to the **http_api_endpoint** HTTP Server for testing the plugin and then code a script to retrieve the logs using a curl command.
 
+#### Download
+
+* [Linux/X86](https://s3.amazonaws.com/store-logos-us-east-1/certification/linux/http_api_endpoint)
+* [Windows/X86](https://s3.amazonaws.com/store-logos-us-east-1/certification/windows/http_api_endpoint.exe)
+
 #### Syntax
 
 ```