https://pact.io logo
Join Slack
Powered by
Hi pactflow team, I'm one of the maintainers of pa...
# pactflow
j
Hi pactflow team, I'm one of the maintainers of pact4s. We were using test.pactflow.io for testing our project using a shared testing username and password, but since the update to the new website it seems that no longer is accepted. Is there a way to continue using this service for pact library developers?
I expect the thing to do is to create an account for pact4s on test.pactflow.io so I can add an api key to the workflow instead (passed in from gh secrets, not plainstring like before)? Would that be possible? PS i'm 99% sure those credentials we were using were publicly available haha
y
hey bud, we’ve now deprecated basic auth, you can use a public token for the time being ( see below ) https://github.com/pactflow/katacoda-workshops/blob/master/pactflow-bi-directional-contracts-intro/step4.md#dont-have-a-pactflow-account I think we need to have a maintainers chat to see if we want to use the pact-foundation.pactflow.io instance and get each project to create a user, to allow us appropriate segregation. cc: @Matt (pactflow.io / pact-js / pact-go)
you can add directly to code or add as a secret. secrets can be problematic for contributor flows
j
mega, thanks for the quick response!
my tests are working again 😻 tyvm
y
yey! sorry for the inconvenience buddy and thanks as always for all the awesome work you do in pact4s chefkiss
m
So sorry Jack. I went through the 
pact-foundation
repositories yesterday but totally forgot that your project sits outside that. I’ll pop an announcement in #C05HCLA3C93 also
j
no worries Matt!
Open in Slack
PreviousNext
Powered by