The way the Sequel gem determines if a table exists or not is by attempting to query it. If it doesn't exist, an error is logged. This is normal and expected, as the schema_migrations table and schema_info tables do not exist the very first time the application is started up. Do not panic! As you can see, the tables are then created in the next statements.
When a pact is published normally (via a PUT to
consumer version resources are automatically created.
To prevent a pacticipant (consumer or provider) being created multiple times with slightly different name variants (eg. FooBar/foo-bar/foo bar/Foo Bar Service), if a new pacticipant name is deemed similar enough to an existing name, a 409 will be returned.
If you get a 409, you have two options.
- Manually create the pacticipant with the desired name (recommended)
- Disable the potential duplicate checking (not recommended).
If the pact broker requires authentication, include '-u yourusername:yourpassword' in the command.
You can create the pacticipant manually through the API browser of the Pact Broker.
Click on the API Browser link at the top right of the index page
pb:pacticipantsrelation in the
Click on the yellow
NON-GETbutton that has a
Enter the following in the
You should see
201 Createdin the
Response Headerssection, and the full JSON document for the newly created pacticipant in the
If you wish to turn this name checking feature off, see the configuration page.