Hey guys, a question about best practices of recor...
# pactflow
m
Hey guys, a question about best practices of record-deployment and can-i-deploy. We are using pactflow.io We are using record-deployment, but we have up to dozen merges (pact published) to integrated environment and maybe one to prod. When our consumer is using can-i-deploy they can't get the both environments from one version. I was looking to use record-release for integrated environment and record-deployment for the prod. This would otherwise work but record-deployment is tagged as
environment
and record-release is tagged as
release environment
. Would this work for can-i-deploy without changes, or do they have to do any modifications for their can-i-deploy call? (edited)
m
We are using record-deployment, but we have up to dozen merges (pact published) to integrated environment and maybe one to prod.
what do you mean by this? Do you deploy multiple versions to the “integrated” environment?
When our consumer is using can-i-deploy they can’t get the both environments from one version.
why do you need to know this?
Is it a linear deployment process. Merge PR 1 -> Deploy to integrated Merge PR 2 -> Deploy to integrated Merge PR n -> Deploy to integrated <some process to agree on prod> Deploy to prod This type thing?
m
Ours is not linear, dozen merges and deployment to integrated. But only one of them is going to prod: PR 1 to PR 12 -> deploy to integrated PR 11 -> deploy to prod
m
what I’m asking is that PR1 and PR12 (and the intermediates) - are they all deployed to the same environment at the same time, or does each PR override the previous one?
m
Sorry, each PR overrides previous one.
m
No probs
so it should be straight forward. Each time you release to the any environment, you just call
record-deployment
with the version that is deployed to it.
Pact Broker will work out the rest
m
Excellent. Thank for help Matt.
👍 1