Add new option to preserveExternalChanges.

[taeold]

This PR make some sweeping changes!

1. We change the default behavior of the SDK so that any un-annotated configuration option that is resettable are given RESET_VALUE. Practically, this means that given a function configuration like this:

export const v2Req = onRequest(
  (req, res) => {
    res.sendStatus(200)
  },
);

And you go ahead and change the memory configuration of the function using GCP Console or gcloud tool, we will revert the memory back to platform default on the next function deploy.

2. You may optionally opt-out of this behavior by setting preserveExternalChanges option:

exports.v1httpPreserve = functions
  .runWith({ preserveExternalChanges: true })
  .https.onRequest((req, resp) => {
    resp.status(200).send("PASS");
  });

functionsv2.setGlobalOptions({ preserveExternalChanges: true });

exports.v2http = functionsv2.https.onRequest((req, resp) => {
  resp.status(200).send("PASS");
});

This change broke a lot of test. I broke up the change for fixing test cases in a separate PR #1254.

[taeold]

Current dependencies on/for this PR:

• master
  • PR Functions SDK v4 #1161
    • PR Add RESET_VALUE configuration value as sentinel value to reset a config option. #1250
    • PR Add new option to preserveExternalChanges. #1253 👈
      • PR Fix broken test. #1254

This comment was auto-generated by Graphite.

[colerogers]

Since spec/v1/providers/fixtures.ts is empty, can we remove it?

[colerogers]

Missing copyright notice, maybe we can have the linter add things like this?

[colerogers]

😅

[taeold]

gotta love ts.

[colerogers]

Is the reset of the whole vpc setting, just removing it?

[taeold]

Reset of the whole thing.

[taeold]

@colerogers It's used in the subsequent PR. Bad PR split!