The version is pulled from the release tag specified in DATAFLOW_RELEASE_TAG at build time.
To add new modules, create a subdirectory in the /v2 hierarchy.
Then you can deploy to a given environment by calling the deploy script with one of "intg", "stge" or "prod":
./bin/deploy-flagship-events.sh --env {env}The first time you build this project (or any time you need to add --clean to
the parameters due to changing DATAFLOW_RELEASE_TAG) an uber-jar will be built
which can take a very long time. Subsequent builds will be very fast, comparatively.
You can watch records being added to the BigQuery table in each environment as API calls are made:
Once validated in Intg or Stge "Stop" and "Cancel" the job so as to not consume extra resources:
Once deployed to Prod "Stop" and "Drain" the previous job: