In order to perform an upgrade of Datashare, you must have completed the initial installation, and have administrative access to perform updates on the deployed resources.
You must have the values for the following variables:
| Name | Required | Description | Default | Example |
|---|---|---|---|---|
| --project-id | No | The GCP Project Id. | Derived from gcloud config list --format 'value(core.project)' |
datashare-demo-1 |
| --oauth-client-id | Yes | The OAuth Client Id. | 8xxxxxxxxxx-xxxxxxxxxxx.apps.googleusercontent.com | |
| --api-key | Yes | The API key. | xxxxxxxxxxxx | |
| --auth-domain | Yes | The auth domain. | datashare-demo-1.firebaseapp.com | |
| --tenant-id | Yes | The IDP tenant Id. | datashare-abcdefg | |
| --fqdn | Yes | The fully qualified domain for the API. | api.datashare.example.com | |
| --data-producers | Yes | The list of users and or domains that should be admins. | cloudysanfrancisco@gmail.com,jeffersonloveshiking@gmail.com | |
| --secret-name-prefix | Yes | The prefix to use for datashare secrets in secret manager | datashare_demo_1 | |
| --tag | No | The container image tag. | dev | dev |
| --region | No | The GCP region for the deployments. | us-central1 | us-central1 |
| --zone | No | The GCP zone for the deployments. | us-central1-a | us-central1-a |
| --marketplace-enabled | No | Flag indicating that marketplace integration should be enabled | Not Applicable | Not Applicable |
- Clone the GitHub repo.
cd datashare-toolkit
- Execute the upgrade script
./upgrade.sh \
--project-id="your_project-id" \
--oauth-client-id="your_oauth-client-id" \
--fqdn="your_fqdn" \
--data-producers="your_data-producers" \
--tag="dev" \
--region="us-central1" \
--zone="us-central1-a"
-
Go to the admin page https://datashare.your-domain.com/admin, and click 'INITIALIZE SCHEMA'.
-
If you're upgrading to Datashare 2.0 for the first time, you must also update the policy table, but running the following script.
UPDATE `datashare.policy` set bigQueryEnabled = true WHERE isDeleted IS FALSE