<@U04S8PLJWMT> do you have some concrete examples ...
# ask-ai
m
@kapa.ai do you have some concrete examples using configs with stream templates?
k
Yes, there are concrete examples of using configs with stream templates in Airbyte. One common scenario is generating streams based on values specified in the connector's configuration. For example, if a user specifies a list of database tables in the connector configuration, each table can become a separate stream. This is known as configuration-based stream generation. Here’s how it works in general: - Configuration-based stream generation: Streams are generated based on values provided in the connector's configuration. For instance, if a user lists several tables or resources in the config, the stream template will generate one stream per item in that list. This is useful for APIs or databases where the user decides what data to sync at setup time. Example use case (from the documentation): > A connector where users specify a list of database tables in the configuration, and each table becomes a separate stream. The stream template uses the configuration values to dynamically generate streams, mapping those values into the stream definitions using the Components Mapping feature. The mapping allows you to interpolate config values into stream properties such as the stream name or endpoint URL. While the documentation provides this as a conceptual example, it does not include a full YAML or JSON config snippet for this specific use case. However, the mechanism is described in detail, and the same approach is used for other dynamic stream generation scenarios, such as fetching issues for multiple GitHub repositories based on a list of repositories retrieved from an API or specified in config. The key is that the template can use config values to generate and customize streams dynamically, saving time and reducing manual configuration effort [Stream Templates](https://docs.airbyte.com/platform/next/connector-development/connector-builder-ui/stream-templates). If you need a step-by-step example, the GitHub Issues API guide demonstrates a similar pattern, though it uses API data rather than direct config values. The same principles apply for config-driven stream generation [Step-by-Step Setup Guide - GitHub Issues API](https://docs.airbyte.com/platform/connector-development/connector-builder-ui/stream-templates#step-by-step-setup-guide---github-issues-api). In summary: - You can use configuration values to generate streams dynamically with stream templates. - The documentation provides conceptual examples and describes the mapping mechanism, but does not include a full config-based YAML example. - The GitHub Issues API example shows the dynamic generation pattern, which can be adapted for config-based scenarios.