We have a question about the usage of policies within
In the official documentation it’s stated that policies are used to set default values on pipeline steps.
While looking at the runner code, we can see that the CPU/memory requests/limits parameters are always overridden by the policy.
Since polices are about default values, one could think that the policy should not override it when it’s actually defined on the pipeline step.
What we would like to do is use the default value for requests/limits when users (dev writting
.drone.yml files for their projects) do not define it.
But if at some point a step needs more CPU/memory, users should be able to override the default value.
Does this use case makes sense ? Will the policy system allow this at some point ? Should we open a PR to propose a change for this ?
Thank you !