Hello, I have question regarding Octavia CLI. In my airbyte instance I have custom connectors (https://docs.airbyte.com/connector-development/cdk-python/), for those I build Docker images and add it in Settings -> Sources -> New connector. And after that I can add new Source. When I’m using octavia import all it does export my source configs. Everything works smoothly. But, when I try to apply these configs to fresh Airbyte instance I’m getting error: Internal Server Error: Could not find configuration for STANDARD_SOURCE_DEFINITION. I believe it’s because this source is not added to Settings -> Sources. How I can solve this? Because if I add it manually it still will have different ID than it’s defined it source configuration file (generated by octavia)

Based on the information provided in the extracts, it seems like you're encountering an issue when trying to apply your source configurations to a new Airbyte instance using Octavia CLI. The error message suggests that the source definition is not found in the new Airbyte instance. One possible reason for this could be that the source definition ID in the new instance is different from the one in the configuration file generated by Octavia. When you manually add a source in the Airbyte settings, it might generate a new ID for the source definition. Unfortunately, the extracts do not provide a direct solution to this issue. However, they do mention a few relevant points: 1. When creating a source definition with Octavia CLI, you need to pass a DEFINITION_ID and RESOURCE_NAME. You first need to get the definition id for the source by running the command

octavia list connectors sources

([source](https://airbyte.com/tutorials/version-control-airbyte-configurations)). 2. Octavia CLI manages Airbyte Configurations as Code (CaC) and not Airbyte Infrastructure as Code (IaC). Thus, Octavia CLI cannot provision an Airbyte instance ([source](https://airbyte.com/tutorials/version-control-airbyte-configurations)). 3. After applying some changes, Octavia creates a state.yaml file in the resource directory with the checksum of the latest configuration applied and the generation timestamp. The state files are instance and workspace specific ([source](https://airbyte.com/tutorials/version-control-airbyte-configurations)). Given these points, you might need to ensure that the source definition ID in your configuration file matches the one in your new Airbyte instance. If they don't match, you might need to manually update the ID in your configuration file. If this doesn't solve your issue, I recommend reaching out to the Airbyte community on their [forum](https://discuss.airbyte.io) or [Slack](https://airbytehq.slack.com) for further assistance.