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

added DRONE_RUNNER_TRUST_ALWAYS env var #2812

Closed
wants to merge 1 commit into from
Closed

added DRONE_RUNNER_TRUST_ALWAYS env var #2812

wants to merge 1 commit into from

Conversation

vyckou
Copy link

@vyckou vyckou commented Sep 3, 2019

variable added for drone-agent and drone-controller services

variable added for drone-agent and drone-controller services
@vyckou
Copy link
Author

vyckou commented Sep 3, 2019

as per #2809 PR comments, added DRONE_RUNNER_TRUST_ALWAYS env var for runners.

This would allow always trust all repositories ignoring their flag in database

@bradrydzewski
Copy link

bradrydzewski commented Sep 7, 2019

Thanks for this!

We are planning to merge this and a few other pull requests on Tuesday and cut the 1.4 release on Wednesday. You also asked some good design questions in #2809 about environment variable vs flag stored in database. I will respond to those in-depth on Tuesday as well to give you some insight into my thinking.

@bradrydzewski
Copy link

hey @vyckou my apologies for the delayed response.

I took some time to evaluate this pull request as well as pull request #2809. I have also taken your feedback into account about pros and cons of direct database updates. We also recently merged a pull request to set the default visibility (see #2826).

Upon further consideration, I think you were correct in your initial suggestion that we should handle this via database update. How do you feel about updating #2809 and re-submitting? The only feedback would be to use the environment variable name DRONE_REPOSITORY_TRUSTED and store this attribute in the Repository struct instead of the Server struct.

I do apologize for the back and forth. Let me know if there is anything I can do to help with #2809. Thanks!

@vyckou
Copy link
Author

vyckou commented Sep 12, 2019

@bradrydzewski I'm glad, that you have changed your mind 😄
#2830 to review

@bradrydzewski
Copy link

closed in favor of #2830 :)

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

Successfully merging this pull request may close these issues.

None yet

2 participants