vmware-archive/fly

The scope for get-pipline should be configurable

Closed this issue · 3 comments

herrjulz commented

we have a centralized concourse server that is used by several teams. We faced the problem that the fly command get-pipline allows other users in one team to download the pipeline yml which exposes all credentials from the user who set up the pipeline.

It would be great to be able to limit the scope of the get-pipeline command to some configurable ways like:

  1. Nobody can execute get-pipeline
  2. only the person who set the pipeline can execute get-pipeline
  3. the whole team can use get-pipeline
concourse-bot commented

Hi there!

We use Pivotal Tracker to provide visibility into what our team is working on. A story for this issue has been automatically created.

The current status is as follows:

  • #141018823 The scope for get-pipline should be configurable

This comment, as well as the labels on the issue, will be automatically updated as the status in Tracker changes.