Hi everyone, it seems like every connector is implemented in some way differently – is there any golden standard example? Makes me wary that there isn’t anything guard railing implementation which makes connectors more prone to fail. Understand that each API is different (from just API keys, to existing libraries, etc.) but I’d thought that there is at least some consistency

A message from kapa.ai

Which ones are “Airbyte Certified”?

@kapa.ai Which ones are “Airbyte Certified”?

A message from kapa.ai

@Marcos Marx (Airbyte) ah, thanks 😛

Airbyte Certified connectors are those that follow the best practices for connector development as mentioned in the [Best Practices](https://docs.airbyte.com/connector-development/best-practices) documentation. These connectors have passed a high-quality bar and are expected to perform reliably in all production use cases. However, the provided extracts do not specifically list which connectors are Airbyte Certified.

@kapa.ai do you have an example link to one that is “Airbyte Certified”?

A message from kapa.ai

https://docs.airbyte.com/integrations/ you can filter based on Release Stage

Got it @Marcos Marx (Airbyte), appreciate the help. Just following up though, when looking at the generally available ones, I can see that some pass the entire config as kwargs while others pass extracted values already — again, understand that each API is different but would have expected that there would be a standard such as only passing it as kwargs or only passing already extracted values How is Airbyte solving this?

There isn’t any strict rules for that today. Most connectors I reviewed use the complete config and sent to the stream class.

I see, well thanks anyways @Marcos Marx (Airbyte) Will check this out more 🙂