IssueTracker

We ran into an issue trying to deploy a Cloud Function from the "master" branch in a Cloud Source Repository. Our assumption was that the function gets redeployed if we commit a change to the master branch and update the deployment, but that is not the case.

Expanded config:

resources:
- name: BUCKET_NAME
  properties:
    location: europe-west3
    storageClass: REGIONAL
  type: storage.v1.bucket
- name: master-cdn-cache
  properties:
    entryPoint: cache
    eventTrigger:
      eventType: providers/cloud.storage/eventTypes/object.change
      resource: projects/PROJECT_ID/buckets/BUCKET_NAME
    function: master-cdn-cache
    location: us-central1
    sourceRepository:
      branch: master
      repositoryUrl: https://source.developers.google.com/p/PROJECT_ID/r/REPO_NAME
      sourcePath: functions/cache
    timeout: 30s
  type: cloudfunctions.v1beta2.function

Upon running `gcloud deployment-manager update`, even though the function source code in the master branch was updated, the function IS NOT redeployed.

The documentation of the relevant "version" field leaves room for interpretation (https://cloud.google.com/functions/docs/reference/rest/v1beta2/projects.locations.functions#sourcerepository):

    Union field version. The version of a function. Defaults to the latest version of the master branch. version can be only one of the following: [...]

In the absence of this feature (redeploying a function from a branch on change), the documentation could at least clarify that functions are only redeployed when one of the parameters has changed.