Hello again. I'm seeing an issue on my end when I ...
# pact-broker
j
Hello again. I'm seeing an issue on my end when I run can-i-deploy. It seems that the answer is always no. My consumer has already published its pacts to the branch and the pact tests themselves are passing on both the consumer and the provider, but my output looks similar to the following:
Copy code
Computer says no ¯\_(ツ)_/¯

CONSUMER                | C.VERSION  | PROVIDER                 | P.VERSION | SUCCESS? | RESULT#
------------------------|------------|--------------------------|-----------|----------|--------
foo-consumer            | git-hash.. | bar-provider             | ???       | ???      |        

WARN: It is recommended to specify the environment into which you are deploying. Without the environment, this result will not be reliable.
There is no verified pact between the latest version of foo-consumer (git-hash) and version git-hash of bar-provider
y
What command are you providing Also the warning
```WARN: It is recommended to specify the environment into which you are deploying. Without the environment, this result will not be reliable.
There is no verified pact between the latest version of foo-consumer (git-hash) and version git-hash of bar-provider```
j
the CI uses the following command
Copy code
if [ "$CI_GIT_BRANCH" = "main" ]; then pact-broker can-i-deploy \
     --pacticipant=$PROVIDER_NAME \
     --broker-base-url=$PACT_BROKER_BASE_URL \
     --version $CI_GIT_COMMIT \
     --broker-token=$PACT_BROKER_TOKEN; \
     fi
y
specify the environment
☝️ 1
or tag
of the env you want to deploy too, otherwise how does it know which env to do the checks against
j
kk. I'll do the environment because this is during my merge to main, so we haven't tagged yet
would it be required that a pact be published by the consumer with the same environment?
because in the previous state no environment was specified by either.