The Wayback Machine - https://web.archive.org/web/20210807180028/https://github.com/topics/consumer-driven-contracts
Skip to content
#

consumer-driven-contracts

Here are 75 public repositories matching this topic...

bethesque
bethesque commented Jul 22, 2021

Please add support for the following keys to be used in the consumer version selectors when fetching pacts for verification:

{ "deployedOrReleased": true }

{ "deployed": true }

{ "released": true }

{ "environment": "<env name>" }

{ "consumer": "<name>" } // this may already be supported, please add it if not

These keys can be used in various combinations ( eg. `{ "env

bethesque
bethesque commented Jul 22, 2021

Please add support for the following keys to be used in the consumer version selectors when fetching pacts for verification:

{ "deployedOrReleased": true }

{ "deployed": true }

{ "released": true }

{ "environment": "<env name>" }

{ "consumer": "<name>" } // this may already be supported, please add it if not

These keys can be used in various combinations ( eg. `{ "envir

tn185070
tn185070 commented Jun 22, 2021

Is your feature request related to a problem? Please describe.
We utilize contract tests to test our projects and rely on a passing build to signify that our project is working. However we have seen that passing contract tests is not necessarily a sure indicator of a project's status. If a contract definition is bad then the generateTests goal of the spring-cloud-contract-maven-plugin will ju

bethesque
bethesque commented Jul 9, 2021

Future documentation for this feature:

To delete pacts for a specific tag.

  • Open the Pact Broker and click "show latest tags"

  • Scroll to the row for the consumer/tag that you wish to delete.

  • Click on the "..." icon for that row

  • Select "Delete pacts for tag <tag>"

  • You will see a prompt with the text

    This will delete the pacts for provider <provider> and all ver
    
bethesque
bethesque commented Jul 22, 2021

Please add support for the following keys to be used in the consumer version selectors when fetching pacts for verification:

{ "deployedOrReleased": true }

{ "deployed": true }

{ "released": true }

{ "environment": "<env name>" }

{ "consumer": "<name>" } // this may already be supported, please add it if not

These keys can be used in various combinations ( eg. `{ "envir

PactSwift
mefellows
mefellows commented Oct 4, 2020

Problem Statement

Provide resources to help new users become proficient in Pact and PactSwift

💬 Task Description

Create an end-to-end workshop based on the canonical pact one (https://github.com/pact-foundation/pact-workshop-js).

👩‍🔧 Technical Design Notes

Suggest using the JS provider as the "backend" for the workshop, to both reduce the effort required in this workshop and

KARtoken - is our version of Bitcoin but designed for the automotive space!! We developed our own coin / token to help anyone, who wants to own any car or truck they want to own. Think of it has a bank, insurance and car maintenance rolled into one company, and providing these services in one simple payment per month.
  • Updated May 6, 2019

Improve this page

Add a description, image, and links to the consumer-driven-contracts topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the consumer-driven-contracts topic, visit your repo's landing page and select "manage topics."

Learn more