Hi, Is there ever a valid case to have multiple ve...
# pact-broker
j
Hi, Is there ever a valid case to have multiple versions of a contract be tagged in a specific environment E.g. between service A & B, both versions X (older version) and Y are tagged with the environment ‘dev’? It’s causing issues in our pipelines that record deployment isn’t removing the environment from the older contract and intermittently the can-i-deploy is picking up the older contract
I’ve found a history of deployments (deployedVersions to be exact) and undeployment timestamps for version X but just not sure why it keeps coming back as our CI system isnt deploying version X anymore
We managed to resolve it as version X had for some reason been “released” so regardless of when a new contract was deployed, it kept showing as being active until we ended support. Fingers crossed we dont see the issue again