Hi! I am implementing a devops pipeline with octavia on our company and I just thought it would be an interesting idea to have source definitions also be deployed by octavia. I thought of it because of two reasons: 1. It would be easier to create source definitions for custom conectors in one place and just have octavia apply it 2. Sources that reference custom source definitions have to replace the definition id (at least until https://github.com/airbytehq/airbyte/issues/10981 gets implemented) on multiple airbyte instances, because UUID for them is different. This would be the same solution as connections reference the source directly instead of the source uuid. Would this be a good solution/possible? Is there a better way to deploy custom conectors on devops?

Thank you @Marcelo Pio de Castro for this valuable feedback. I think you are right that octavia should also be able to manage definitions. And you're also right that the issue you linked should be implemented first. I'll create an issue for this specific feature.