Hi, I wonder if I can have some clarity on what I ...
# pact-broker
j
Hi, I wonder if I can have some clarity on what I am seeing? In my CI/CD (CircleCI) pipeline I call
pact-broker record-deployment --environment "main" --pacticipant "service" --version "74332f5"
and I get the output
Recorded deployment of service version 74332f5 to main environment in the Pact Broker
. I then call the command
pact-broker create-version-tag --pacticipant "service" --version "74332f5" --tag "main"
. This is so that we support the legacy implementation of using tags and then have a history of environments to migrate over to in the future. The problem I am seeing is that whenever I call both of these commands, the contract has a tag of main but not an environment against it. If I just call
create-version-tag
then both an environment and tag are added to the contract but I’m not sure why. Even weirder still I use this same combination of record deployment and create version tag in downstream jobs and they tag and set environment with no problem
m
hmm interesting. How are you verifying that out of interest? UI or API?
j
I’m going to the UI