Disable "Edit Steps"?

Features Requests
1

Hi there.

Our pipelines are managed by Terraform entirely, and we don’t want to allow editing the pipeline’s steps from the Web UI. I’d like to request a feature, maybe a pipeline setting that would be “Allow Edit Steps from the UI”. if disabled, it would replace the “Edit Steps” button with a “View Steps” button, and a read only view of the steps.

The idea here is simply to avoid accidental changes.

2

Hello, @donal! Thank you for your feedback, I will share it with the team.
You can also try the following - you can create a new team and add the pipelines you’d like to be “read only” for the team members to it. “Read only” is the default access permission for a pipeline when you add it to a team. You can read more about this in the Docs.

Best!
Karen

3

We are also Terraforming our pipelines. We’ve disabled edit access for most users. Only Admins can edit in the web UI. That’s eliminated drift for the most part.

But it would be nice to be able to lock out changes to the steps editor in the Web UI altogether.

So +1 from me on this feature.

4

Hi @donal, @ian-persona,

I am from the product team at Buildkite. We are currently working on a feature that will allow you to have 1 yaml definition that is applied to all pipelines across your organisation. This feature will be ready in around a month time and will be an enterprise feature. I will notify you once it’s ready so you can take a look and see if it is interesting for you.

Just a note of curiosity for me, would having one yaml step definition in that edit steps screen across all of your pipelines solve your need? Would you need multiple options to choose from?

Thanks,
Oz

1 Like
5

Thanks for the replies. Restricting edit access to admins is a great idea,and actually works really well to encourage people to not try and change the pipeline in the web UI at all!

@ozdenyilmaz - we can certainly wait a month and see if it’s suitable. One yaml step across the pipelines might be workable, depending on agent requirements but we may be open to changes in our agent requirements on our side if it helps

6

Hi again @donal, when you say agent requirements do you mean the queue definitions? Are you defining the queue that the steps need to run on in that yaml and that’s why you’d need multiple templates across pipelines? Maybe I am completely off the mark here so please tell me that my guess is wrong!

7

Exactly. A slight edge case but one of our pipelines also sets BUILDKITE_BUILD_CHECKOUT_PATH to force it to share a checkout directory with another pipeline (for caching and performance)

8

Thanks for explaining @donal this is very helpful. I will message you once the feature is ready for you to have a look!

1 Like