Missing parameters for pipeline creation about pybuildkite HOT 7 CLOSED

I totally agree with you! No aspersions received =). If you'd like to submit a patch I'd be happy to accept. It will be a day or two before I'm freed up to handle the pip packaging but I will!

from pybuildkite.

@pyasi are you still actively maintaining this repo? It looks like there hasn't really been any activity since last fall.

from pybuildkite.

@GMNGeoffrey Yes, there has not been much activity lately but I am interested in continuing to maintain this. I agree that given the frequency of changes to the Buildkite API that kwargs is likely a better long term decision.

from pybuildkite.

Great! I'm happy to send a patch if you can deal with releasing a new pip package :-)

from pybuildkite.

Didn't mean to cast aspersions wrt "lack of activity". In my opinion minimal-maintenance things are generally much better than things where the developer pretends that they're actually going to stay on top of everything forever :-D

from pybuildkite.

#82 was just merged, which goes part of the way to solving this problem.

My personal opinion is that they shouldn't be replaced by a general kwargs argument. One of the most important reasons to use an API client like this over using requests.post() directly is type-safety. I would much rather see individual options added as necessary, so that I can more easily verify my own code is doing the right thing.

from pybuildkite.

(it would be great if a new release could be created that includes #82)

from pybuildkite.