opened
- #452 Verifier cli: consumer version selectors - multiple --consumer-version-selectors arguments are confusing and not honored in all cases
+ #718 chore(deps): update ruff to v0.5.0
-
opened by lautwe in pact-foundation/pact-reference
+
opened by renovate[bot] in pact-foundation/pact-python
+
2 files changed ++2 --2
@@ -339,20 +339,15 @@
-
YOU54F
- commented on
- #1807 Allow Pact generation in Android Automation tests
-
-
-
-
opened by canny[bot] in pact-foundation/pact-jvm
-
- Matt Fellows - July 9, 2021
- I must have missed this idea, but the biggest problem is adding matchers. Without matchers, a provider side test with Pact might be painful. One option would be to just default to a like matcher, so that it just looks at shape.
-This would work nicely, however, with the Pactflow bi-directional feature (https://docs.pactflow.io/docs/workshops/bi-directional)
+
renovate[bot]
+ created new
+ branch
+ renovate/ruff
+ in
+ pact-foundation/pact-python
@@ -361,17 +356,19 @@ This would work nicely, however, with the Pactflow bi-directional feature (https
-
Saup21
- created new
- branch
- PACT-2105-new-label-api
- in
- pact-foundation/pact_broker
+
YOU54F
+ commented on
+ #162 Re-implement Pact Broker Client in a language that can be compiled to a standalone binary
+
+
opened by canny[bot] in pact-foundation/pact_broker-client
+
I've been slowly chipping away at this off and on
+https://github.com/YOU54F/pact_cli
+
@@ -383,15 +380,18 @@ This would work nicely, however, with the Pactflow bi-directional feature (https
YOU54F
commented on
- #164 Support environment/releases on describe-version
+ #162 Re-implement Pact Broker Client in a language that can be compiled to a standalone binary
opened by canny[bot] in pact-foundation/pact_broker-client
- Rafael Anachoreta - February 8, 2022
- Alternatively, a specific command to return the deployed/released versions on a specific environment would work too
-pact-broker describe-deployed --environment=production --pacticipant="My Consumer"
+ cspengl - January 18, 2022
+ Hi folks, I really like this idea. I recently found myself in the exact situation you are describing. I was looking for an easy way to just download the pact broker cli as a standalone executable similar to how I can install kubectl for kubernetes.
+Looking towards widely used CLIs like kubectl, docker-cli or helm which perform very similar tasks, especially Golang sounds like a good option to me.
+ Matt Fellows - January 25, 2022
+ cspengl: thanks. Can you please elaborate specifically on the issues you experienced when using the standalone CLI (see https://github.com/pact-foundation/pact-ruby-standalone/releases)?
+(not discounted that you had issues, but looking for customer feedback here).
commented on
- #683 Autogenerate API specs from all pacts
+ #162 Re-implement Pact Broker Client in a language that can be compiled to a standalone binary
-
opened by canny[bot] in pact-foundation/pact_broker
+
opened by canny[bot] in pact-foundation/pact_broker-client
- Matt Fellows - February 9, 2022
- I'm surprised to see that this request doesn't exist already, as I know I've been a proponent of the same thing! It must be somewhere, but I couldn't find it here. In any case - yes, want! :)
+ Matt Fellows - January 18, 2022
+ I think it's also worth making mention, that the backwards compatibility with the pact broker built into the current CLI would need replicating. I'm not sure what this would translate to effort wise, but is a key consideration.