Skip to content

Latest commit

 

History

History
39 lines (26 loc) · 1.34 KB

README.md

File metadata and controls

39 lines (26 loc) · 1.34 KB
Raw

Fleet Engine Auth Sample Scripts

When the application is run, a menu option appears. The first option validates that the configured service accounts are working as expected. This is helpful when first setting up your GCP project.

The other options run hardcoded commands such as:

  1. Create a vehicle with a random id
  2. Search for a random set of trips and display to the terminal

You can use these examples as a starting point when first using the generated client libraries.

For directions on how to call Fleet Engine in your project, see: https://developers.google.com/maps/documentation/transportation-logistics/on-demand-rides-deliveries-solution/trip-order-progress/fleet-engine/gapic_client

Configuring

The scripts are configured with a service account to run under. Each service account must be configured according to the instructions in the auth library README.

NOTE: Whatever account the application runs under, MUST have the iam.serviceAccounts.signBlob permission. This is typically acquired through the Service Account Token Creator role.

The service accounts with other configuration options are configured in src/main/java/com/google/fleetengine/auth/sample/LmfsConfiguration.java and src/main/java/com/google/fleetengine/auth/sample/OdrdConfiguration.java

Running

Once configured, simply run:

./gradlew run