Migrating your deployment package to Producer Portal for VM products

Producer Portal supports deployment packages that are hosted in Cloud Storage buckets, which enables support for both API-driven and command-line-driven uploads and version control.

Previously, when you set up your product in Partner Portal, you either set up your deployment package directly in the portal (for simple deployment packages), or you uploaded a deployment package through Google Cloud Console.

If you previously set up your package directly in the portal, you don't need to take any additional steps to migrate your deployment package when your product migrates to Producer Portal. You can also use Producer Portal to directly manage your deployment package after migration, much like how you used Partner Portal to manage it before migration.

If you previously uploaded your deployment package through Partner Portal, and you don't plan to make any updates to your deployment package, then you don't need to take any additional steps to migrate your deployment package when your product migrates to Producer Portal. However, if you want to update your previously-uploaded deployment package after migration, you must set up a Cloud Storage bucket and migrate your deployment package to it.

Migrate your deployment package to a Cloud Storage bucket

For detailed information about setting up a Cloud Storage bucket to host a deployment package, visit Creating your deployment package.

When you create your deployment package, we recommend that you use the mpdev command-line tool, which helps you to automate the test and release process for your deployment packages.