https://pact.io logo
Join Slack
Powered by
Why was publishing a pact removed from PactNet and...
# pact-net
j
Why was publishing a pact removed from PactNet and now only accessible through the CLI, but verifying a pact with a pact broker source is still there? Wouldn't publishing a pact be extremely useful?
m
The aim is to not have all of the client libraries re-implement all of the CLI functionality.
It reduces the ability to add new features across the board quickly, because each language needs to add the change and each client library is maintained by different people
j
It seems like a pretty major part of Pact should be part of each client library though
m
why? What’s the problem with installing a CLI?
j
It adds another step to my pipeline, requires me to curl GitHub every time I run the pipeline, decouples my tests from just the code
It also makes it harder to go between languages if one client library does publish to a broker in code (pact-js)
m
to run a successful Pact pipeline, you would usually require more than just the ability to publish a pact. You would usually also call the 
pact-broker can-i-deploy
command and also the 
pact-broker record-deployment
command, and possibly several others.
It also makes it harder to go between languages if one client library does publish to a broker in code (pact-js)
We’ll be removing that very soon also - sorry 😬
Having code and non-code based versions of what the CLI does also makes it harder to document things, and communicate best practices to people.
We want to simplify that - the boundary is basically “anything to do with testing, goes in the client library” and everything else pretty much goes in the CLI
j
My difficulty with pact-net came from the fact that the docs didn't say I needed the CLI in order to use a broker. in fact, I ended up having to come into this slack and look it up here
m
Yes, that’s a problem that needs addressing. The documentation for Pact .NET is rather sparse
I’m sorry for that confusion. I’m not a .NET developer/maintainer, but we are looking at ways we can help contribute and improve them
💯 1
j
Thanks! I'm just working to get buy in for my client on pact and it's been tough with the state of the docs
💯 1
d
I am also here because I am struggling to get PactNet up and running...I am on a Mac M2 and have downloaded the native libraries. I have also run dotnet build successfully but I don't know what to do next
y
If I am not wrong, PactNet still publishes verification result. Is it going to be moved out to be part of the CLI as well ?
t
@David McGill It sounds like your question might be separate. Maybe give more details in a different thread?
✅ 1
@Yerken T It’s already part of the CLI.
(whether it will be removed from the library in the future is a different question, I think).
👍 1
Open in Slack
PreviousNext
Powered by