WIP: Create contract tests for interaction with Auth service.

[pmacik]

No description provided.

[centos-ci]

Can one of the admins verify this patch?

[alexeykazakov]

We can't relay on OSO-starter to run the broker. Need a better place for that.

[bartoszmajsak]

Maybe the same home as sentry and ike bots? /cc @kbsingh

[alexeykazakov]

Yeah.. it should be preview or prod cluster. @pmacik talk to the SD team.

[pmacik]

@alexeykazakov @bartoszmajsak Thanks for the suggestion, created appropriate SD ticket for that (https://gitlab.cee.redhat.com/dtsd/housekeeping/issues/2383)

[bartoszmajsak]

Who is a provider and who is a consumer here? Or in other words - where can I see auth tests?

[bartoszmajsak]

Few other points

• publishing part ideally should be part of the test code - so we can nicely wrap it as part of test execution rather than a shell script run afterwards
• I would think of contract tests actually touching some real component talking with the underlying service - thinking about it as a "shareable mock" - you mock auth service but excercise some actual logic in the component which communicates with it

[pmacik]

Who is a provider and who is a consumer here? Or in other words - where can I see auth tests?

@bartoszmajsak The provider is the Auth service (PACT_PROVIDER_BASE_URL) while the consumer is the tenant service itself.

It's still a WIP so both contract sides are in the same place, but the auth tests (the provider tests) are the part verifying the pact file taken from broker against a living auth service instance (=test-contract-auth-verify-broker, I plan to move that to the auth service repo and include it in their tests).