for a new integration what are the steps (and can I add them to the docs): • Write integration • Write integration tests • Also write pairwise acceptance test (??? can’t remember if we said this was part of it) • Put this all up for a PR. • Write docs but in a separate PR • Push the image of the integration to docker hub. • Merge both PRs at the same time?

no pairwise acceptance tests

we wanted to encourage a common set of records for consumption by the integration-level tests

ah

okay

we haven't done that yet thought

okay.

can we encourage people to write the docs in the original PR directly instead of interacting via gitbook, but still render the markdown via gitbook?

i’m going to reuse singer-tap-output.txt from TestPosgresDestination.

can we encourage people to write the docs in the original PR directly instead of interacting via gitbook

yes good idea.

as long as we have template and instructions on where they need to put their docs.

I think we wanted to put those records in a docker image

so it's tap-like

and an external artifact that someone can use to develop their integration

okay. i’m going to copy and paste for now,

and then after that i can do figure out how to share it as an image.

want to just focus on getting the integration first.

sounds good

one thing we can do is to create a template tap & target intergation directory in the integration module.

that will help on how we want to structure it and how we want to document