Kwan Lee
11/09/2023, 1:45 AMKwan Lee
11/10/2023, 4:48 PMGabriel Ferrarini
11/13/2023, 12:07 PMdev
Matt (pactflow.io / pact-js / pact-go)
Matt (pactflow.io / pact-js / pact-go)
service-database
builds successfully.
2. The PR for service-roi-core
fails in the “*can-I-deploy*” step because the new endpoint does not exist in any environment, leading to a verification failure.
3. The PR for service-database
is merged and deployed to the development environment only.
4. The PR for service-roi-core
is rechecked and fails again in the “*can-I-deploy*” step because service-database was not deployed to non-prod and production.
5. The PR for service-roi-core
cannot be merged until we manually release service-database to non-prod and production.
Options you listed to address this
a) Create mirror environments for non-prod and production that will have continuous deployments happening to them.
b) Skip the “*can-I-deploy*” step for environments other than dev in the PR validation. This will allow us to merge to main in service-roi-core in the example above, but then the “*can-I-deploy*” step that occurs during the actual deployment to non-prod (depicted in the Pact link above) will most likely fail because the deployment to non-prod in service-database hasn’t happened yet. We would need to perform two manual releases to have everything in non-prod and then two releases to have everything in production.
c) Only run “*can-I-deploy*” for dev in the PR validation and deploy to dev. This would defeat part of the purpose of why we implemented Pact in the first place.Matt (pactflow.io / pact-js / pact-go)
Michael DaSilva
11/30/2023, 4:42 PMMichael DaSilva
11/30/2023, 4:52 PMGabriel Ferrarini
11/30/2023, 5:55 PM