How Pact Distinguishes "latest" for a tag

[zbintliff]

Have a question regarding the broker. It doesn't seem like its finding the latest versions of the tags I'm using.

Our setup:
Version: Git SHA
Tag: branch
Pacts can be pushed locally via go test ./... -tags=pact and also via our CI pipeline when running tests.

We did this way so we can always say give me the "master" (production) version of the pact.

When hitting: https://my.pact.net/pacts/provider/granola/consumer/service-clients/latest/master to get the latest for tag master I get a pact that was created: Fri 27 Oct 2017, 8:36pm +00:00

When I go in HAL browser and look for the specific SHA for the latest master (version 4ff6fe1be3bd1e2a23fc516223460378df2ba938) that pact is created on:"createdAt": "2017-11-01T15:29:34+00:00"

Am I misunderstanding how it attributes the the latest tagged version? I've read the wiki, and I think I'm using tags and versions as recommended there.

Also notice the first page of the broker references the pacts that I deployed over a week ago (on some random branch). We've been iterating pretty quickly on pacts. I probably deployed 5 pacts for this consumer/provider pair today alone

[zbintliff]

This is my fault: https://github.com/pact-foundation/pact_broker/wiki/Configuration#ordering-versions-by-date

Now, if I'm using the docker image. Would you recommend I build FROM your and host our container, or PR allowing the option in the config.ru?

[mefellows]

I would just use our image as the base, create a custom config.ru file and do your ADD config.ru to override the default.

IIRC there is also a runtime toggle where you can configure this via the DB (no API exposed as of yet).

Try this at your own risk (i.e. back up first)

insert into config (name, type, value, created_at, updated_at) values ('order_versions_by_date', 'boolean', '1', now(), now());

[zbintliff]

Great thanks!

[bethesque]

I've just put out a new version of the docker broker (2.6.0-3) that will load the configuration from the database DiUS/pact_broker-docker@d373f48

Grab the latest copy, and run the line that Matt suggested, and you won't need a custom build.

[mefellows]

Amazing.