This page covers the process of submitting your page for testing and review.
Before you begin
- Make sure that you have reviewed and met all the requirements for listing your solution.
- Make sure that you have reviewed and met all the requirements for packaging your solution.
- Configure payments so that you can be paid for your solution's usage.
- Test your solution end-to-end.
Add marketing information and documentation
To edit the solution, click the solution ID.
Complete the Solution Details and Documentation & Support sections.
Every solution must be accompanied by a Google Cloud Platform-specific Getting Started document that helps your customers with detailed deployment and configuration steps for your solution. The documentation must be created and maintained by you on your website. We suggest that you co-brand the page with the Google Cloud Platform logo, available at the Cloud Connect site. (Note that Cloud Connect requires you to register to access the site.)
The document should provide step-by-step guidance for the customer's journey, starting with the solution page on the GCP Marketplace site and extending all the way through to the deployment and post-deployment maintenance of the solution. We recommend including screenshots throughout the document, in addition to the text instructions.
The document should provide the customer with guidance on what inputs they will have to provide for to a successful deployment, such as:
The recommended machine configuration, disk sizes, zones, and so on
If the customer has to open any ports (particularly 80 or 443)
Whether the required ports are opened by default, or the customer has to open them during the process of deployment
Add next steps
The document should list any additional commands needed to configure the solution.
If your solution requires a login, the document should outline if and how the customer will gain access to an admin page or console URL, and how login credentials can be obtained.
The document should also outline how the customer:
Can SSH into the virtual machine instance
Can access a list of licenses, along with source code, for any open source components on the instance
Can check the status or health of the application
For additional guidance, you can refer to these example pages that have been developed for other solutions in GCP Marketplace:
After you have finished the draft of your Getting Started document, please email the URL of your draft to your assigned Partner Engineer for review and feedback.
Setting and retrieving application user credentials
If your solution requires a login, it must use automatically generated passwords. The username and password key values can be set in the solution's metadata and read during instance or application startup using the following format:
If your solution requires a login, then be sure to complete these fields in Partner Portal, under Edit deployment package.
The password is auto-generated by the GCP Marketplace and can be accessed from the instance using the following command:
curl -H "Metadata-Flavor: Google" http://metadata.google.internal/computeMetadata/v1/instance/attributes/<solution>_user_password
Make the image public
You must make your image publicly available so that your customers can deploy
it to their Compute Engine instances. To make the image public, use the
GCP Console, or the
gcloud command-line tool:
In your public project, under Compute Engine, go to the Images page.
Select your image, as shown below:
If you don't see an info panel on the top-right, click Show Info Panel.
In the info panel, in the Add Members field, enter
allAuthenticatedUsers, and from the Select a role menu, select Compute Image User.
Click Add to make your image public.
Use the following
gcloud beta command in
Cloud Shell, or on your local
gcloud beta compute images add-iam-policy-binding IMAGE_NAME --member=allAuthenticatedUsers --role=roles/compute.imageUser
Submit your solution
Now you can submit your solution! This starts the automatic validation process, and notifies your contact at Google that your submission is ready for review.
If you find a mistake in your solution, or if your contact at Google requests changes to it, you can always cancel your submission, make changes to it, and then submit it again.