Experiencing frequent request for manual approvals on all our protected repository, even when no changes are made to the drone-file.
We recently implemented a validation and environment extension to our workflow. Basically, our validation extension validates a custom YAML file (not drone-file) without tempering with the drone-file used for pipeline deployment. Then uses its content to validate users/repository before each pipeline triggers. This only sends response to the server with an appropriate HTTP code and error message, if users are permitted or not. So, not expecting this to be causing the issue since no modification is done to the original signed drone-file.
The Environment extension on the other-hand issues couple of environment variables to the pipeline steps during each runs. I’m not expecting this to be causing the issue either, since the environment variables are provided to pipeline steps by the runners after each pipelines have be trigger and running. Clarify, if this isn’t the case.
Is there a way to implement both extensions and still ensure we do not have to manually approve each repository unless a user actually makes changes to the drone-file?