Skip to content

Document that Custom Build Strategy is disabled by default and how to enable it #4081

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

Closed
php-coder opened this issue Apr 5, 2017 · 5 comments
Assignees

Comments

@php-coder
Copy link

Inspired by the question on IRC:

tjololo> hi, is it possible to "enable" Custom Builds when you are using "oc cluster up". I'm trying to test a Custom Builder, but when I try to register the BuildConfig with custom as build strategy I get a error message saying: "build strategy Custom is not allowed."

It turns out that our documentation doesn't cover the current state of the Custom Build Strategy:

  • nowhere is mentioned that this is disabled by default (and why)
  • there is also no instructions how to enable it

I believe that at least the following places should be updated:

Related issues:

CC @bparees @coreydaley

@bparees
Copy link
Contributor

bparees commented Apr 5, 2017

actually the doc clearly states that is it not disabled by default, so the question would be why is it disabled in oc cluster up? That is a question for @csrwng

By default, all users that can create builds are granted permission to use all build strategies (Docker, Source-to-Image, and Custom).

and i think this covers "instructions on how to enabled it":
https://docs.openshift.org/latest/admin_guide/securing_builds.html#restricting-build-strategies-to-a-user-globally

(but again we claim it's enabled by default, so if it's not we need to sort that out).

@csrwng
Copy link

csrwng commented Apr 5, 2017

Actually it should not be (enabled by default):
https://bugzilla.redhat.com/show_bug.cgi?id=1380462
openshift/origin#11411

@bparees
Copy link
Contributor

bparees commented Apr 5, 2017

assigning to @coreydaley then since the docs should have been updated when that change was put in.

@vrutkovs
Copy link
Member

The docs are not updated yet, Securing builds by strategies states:

By default, all users that can create builds are granted permission to use all build strategies (Docker, Source-to-Image, and Custom).

@bparees
Copy link
Contributor

bparees commented Apr 11, 2017

@vrutkovs yes that's why this issue is still open....

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

5 participants