Continuing thread https://pact-foundation.slack.com/archives/C9VBGLUM9/p1723003405446749?thread_ts=1722947907.581659&cid=C9VBGLUM9 Thank you Matt, also for the extra reminder about

can-i-deploy

, we won't use that for now for the reasons mentioned (and some others) As for the

--verification-exit-code=0

, I do have this set in my Makefile but the results are still as shown in the screenshots. On further inspection, I can also not find my OAS file anymore within Pactflow, perhaps I am overwriting it somehow? Currently I use this:

publish_pacts:
	"${PACT_CLI}" publish pacts/ --consumer-app-version 1.0.0 --broker-base-url <https://XXXXX.pactflow.io/> 
	@echo 'trust me' > report.txt
	@echo "\n========== STAGE: publish provider contract (spec + results) - success ==========\n"
	PACTICIPANT=${PACTICIPANT} \
	"${PACT_CLI}" pactflow publish-provider-contract \
	/app/${OAS_FILE_PATH} \
	--provider ${PACTICIPANT} \
	--provider-app-version ${GIT_COMMIT} \
	--content-type ${OAS_FILE_CONTENT_TYPE} \
	--verification-exit-code=0 \
    --verification-results /app/report.txt \
    --verification-results-content-type text/plain \
    --verifier "Provider not actually verified, we will implement this after FE"

Which seems to Push two integrations in PactFlow the one with missing FE - >

??? & BE-openapi-spec

and the integration ->

Frontend & Backen OpenAPI

. I'm guessing what I'm doing is not the right approach?