Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

GCS Semver File Does not seem to be updating #112

Open
xtreme-shane-lattanzio opened this issue May 22, 2020 · 1 comment
Open

GCS Semver File Does not seem to be updating #112

xtreme-shane-lattanzio opened this issue May 22, 2020 · 1 comment

Comments

@xtreme-shane-lattanzio
Copy link

xtreme-shane-lattanzio commented May 22, 2020

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
Copy link

mamachanko commented Jul 29, 2021

@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.

#128

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants