concourse / semver-resource

automated semantic version bumping
Apache License 2.0
97 stars 105 forks source link

GCS Semver File Does not seem to be updating #112

Open xtreme-shane-lattanzio opened 4 years ago

xtreme-shane-lattanzio commented 4 years ago

In a pipeline that I am simply trying to bump a semver file. If the resource is

- name: semver-version
  type: semver
  source:
    driver: gcs
    bucket: lf-semver-version
    key: VERSION
    json_key: ((GCPQueuedReportsBucketCredentials))

and the usage is

- name: bump-minor
  plan:
    - put: semver-version
      tags: ["private-worker"]
      params: {bump: minor}

Why is it getting the file correctly and then putting the exact same file without bumping?? This screenshot is with 6.2.0 in the bucket:

Screen Shot 2020-05-22 at 12 16 30 PM

Basically it is bumping the version but not in the GCP file at all and returning the same version. I can get it to bump in concourse using the same version file when I change it to

- name: bump-minor
  plan:
    - get: semver-version
      tags: ["private-worker"]
      params: {bump: minor}
    - put: semver-version
      params: {file: semver-version/version}

But in that way the actual file still doesn't update you just get:

Screen Shot 2020-05-22 at 12 17 43 PM

Any idea why the GCS file is not updating? With the get/put flow, it at least bumps the version in concourse metadata but the atomic put flow doesn't seem to work at all. HALP!!

mamachanko commented 3 years ago

@xtreme-shane-lattanzio make sure that the configured account has the required permissions. Storage Object Admin does the job. Maybe it can get away with even fewer permissions.

https://github.com/concourse/semver-resource/issues/128