Adapt to new way of fetching APIs - it comes with code generation

Author: Sebastian Thiel

Diff for: README.md

@@ -17,18 +17,13 @@ to one that you just build. Typical invocations would look like this:
 (cd ../generator && cargo build) && just MCP=$PWD/../generator/target/debug/mcp update-drivers
 ```
 
-### Forcefully regenerating/rebuilding crates even if they errorred before
+### Forcefully regenerating/rebuilding crates even if they failed to generate/build before
 
 The system will remember generator and cargo errors, and not attempt to work on the affected APIs again, unless these files are cleared.
-This can be done manually, or by force.
+This can be done manually, but most of the time you will want to refresh everything, and check for errors.
 
 ```
-just refresh-with-force
-```
-
-From there you would usually go with the following to gather all error data with refreshed code:
-```
-just collect-errors
+just refresh-all
 ```
 
 ### Forcefully update the Makefile after a change affecting the mapped index

Diff for: etc/api/container/v1beta1/spec.json

@@ -7,7 +7,7 @@
   "canonicalName": "Container",
   "fullyEncodeReservedExpansion": true,
   "version": "v1beta1",
-  "revision": "20190628",
+  "revision": "20190812",
   "title": "Kubernetes Engine API",
   "description": "Builds and manages container-based applications, powered by the open source Kubernetes technology.",
   "ownerDomain": "google.com",

Diff for: etc/api/runtimeconfig/v1/spec.json

@@ -7,7 +7,7 @@
   "canonicalName": "Cloud RuntimeConfig",
   "fullyEncodeReservedExpansion": true,
   "version": "v1",
-  "revision": "20190819",
+  "revision": "20190822",
   "title": "Cloud Runtime Configuration API",
   "description": "The Runtime Configurator allows you to dynamically configure and expose variables through Google Cloud Platform. In addition, you can also set Watchers and Waiters that will watch for changes to your data and return based on certain conditions.",
   "ownerDomain": "google.com",

Diff for: etc/api/runtimeconfig/v1beta1/spec.json

@@ -7,7 +7,7 @@
   "canonicalName": "Cloud RuntimeConfig",
   "fullyEncodeReservedExpansion": true,
   "version": "v1beta1",
-  "revision": "20190819",
+  "revision": "20190822",
   "title": "Cloud Runtime Configuration API",
   "description": "The Runtime Configurator allows you to dynamically configure and expose variables through Google Cloud Platform. In addition, you can also set Watchers and Waiters that will watch for changes to your data and return based on certain conditions.",
   "ownerDomain": "google.com",

Diff for: etc/api/servicecontrol/v1/spec.json

@@ -7,7 +7,7 @@
   "canonicalName": "Service Control",
   "fullyEncodeReservedExpansion": true,
   "version": "v1",
-  "revision": "20190816",
+  "revision": "20190810",
   "title": "Service Control API",
   "description": "Provides control plane functionality to managed services, such as logging, monitoring, and status checks.",
   "ownerDomain": "google.com",

Diff for: etc/api/servicemanagement/v1/spec.json

@@ -7,7 +7,7 @@
   "canonicalName": "Service Management",
   "fullyEncodeReservedExpansion": true,
   "version": "v1",
-  "revision": "20190809",
+  "revision": "20190816",
   "title": "Service Management API",
   "description": "Google Service Management allows service producers to publish their services on Google Cloud Platform so that they can be discovered and used by service consumers.",
   "ownerDomain": "google.com",

Diff for: etc/api/toolresults/v1beta3/spec.json

@@ -1,13 +1,13 @@
 {
   "kind": "discovery#restDescription",
-  "etag": "\"9eZ1uxVRThTDhLJCZHhqs3eQWz4/uhyHOYXYldiARLSzJi77wNDgCvw\"",
+  "etag": "\"9eZ1uxVRThTDhLJCZHhqs3eQWz4/BXvf1UotF2LiymSOKSxDnp5W19c\"",
   "discoveryVersion": "v1",
   "id": "toolresults:v1beta3",
   "name": "toolresults",
   "canonicalName": "Tool Results",
   "fullyEncodeReservedExpansion": null,
   "version": "v1beta3",
-  "revision": "20190821",
+  "revision": "20190822",
   "title": "Cloud Tool Results API",
   "description": "Reads and publishes results from Firebase Test Lab.",
   "ownerDomain": "google.com",
@@ -2478,6 +2478,7 @@
           "enum": [
             "anr",
             "availableDeepLinks",
+            "blankScreen",
             "compatibleWithOrchestrator",
             "completeRoboScriptExecution",
             "crashDialogError",
@@ -2494,6 +2495,7 @@
             "nativeCrash",
             "nonSdkApiUsageReport",
             "nonSdkApiUsageViolation",
+            "overlappingUiElements",
             "performedGoogleLogin",
             "performedMonkeyActions",
             "startActivityNotFound",
@@ -2529,6 +2531,8 @@
             "",
             "",
             "",
+            "",
+            "",
             ""
           ],
           "properties": {},

Diff for: justfile

@@ -17,7 +17,7 @@ help:
     cat <<EOF
     Run 'just --list' for more details, here is an overview
     -- Used most often... ---------------------------------------------------------------------------)
-    'refresh-pruned-specs' and 'refresh-with-force'
+    'refresh-pruned-specs' and 'refresh-all'
     'gen/all' and 'gen/cargo check'
     -- The source of it all -- first mentioned serve as input for these mentioned later -------------)
     'refresh-google-api-index'  and 'fetch-api-specs-pruned' and 'fetch-api-specs-google'
@@ -57,11 +57,11 @@ update-drivers: _map-api-index mcp
 
 # fetch API specifications from Google's discovery service, based on the list of ones we know work
 fetch-api-specs-pruned: _map-api-index mcp
-    {{MCP}} fetch-api-specs {{API_INDEX_MAPPED_JSON}} {{SPEC_DIR}}
+    {{MCP}} fetch-api-specs {{API_INDEX_MAPPED_JSON}} {{SPEC_DIR}} {{OUTPUT_DIR}}
 
-# fetch API specifications from Google's discovery service, based the entire index of available APIs
+# fetch API specifications from Google's discovery service, based the entire index of available APIs, and regenerate code
 fetch-api-specs-google: refresh-api-index
-    {{MCP}} fetch-api-specs {{API_INDEX_JSON}} {{SPEC_DIR}}
+    {{MCP}} fetch-api-specs {{API_INDEX_JSON}} {{SPEC_DIR}} {{OUTPUT_DIR}}
 
 # fetch latest API specifications known to be working, just make it work!
 refresh-pruned-specs: fetch-api-specs-pruned update-drivers
@@ -73,6 +73,8 @@ refresh-with-force:
     just fetch-api-specs-google
     just update-drivers
 
+# clear errors, fetch latest index from google, and fetch all specs, run cargo check and doc
+refresh-all: refresh-with-force collect-errors
 
 any_error := "*"
 # valid prefixes: generator or cargo
@@ -91,11 +93,9 @@ show-errors prefix=any_error:
         cat "$fp"
     done
 
-# Best after 'refresh-with-force', it generates all code and runs cargo against it, collecting errors
+# Best after 'refresh-all', it generates all code and runs cargo against it, collecting errors
 collect-errors:
     just mcp 
-    just gen-all || true
-    just update-drivers 
     just gen-check  || true
     just update-drivers
     just gen-doc  || true