Andrew Nessin
07/10/2023, 12:15 PMkapa.ai
07/10/2023, 12:15 PMkapa.ai
07/10/2023, 12:16 PMoctavia list command, and then generate the YAML configuration by running octavia generate source <DEFINITION_ID> <SOURCE_NAME> or octavia generate destination <DEFINITION_ID> <DESTINATION_NAME>. [source](https://docs.airbyte.com/cli-documentation) 2. After generating the YAML files, you can make the necessary changes to the connector version in the YAML file. 3. Once you've made the changes, you can propagate these changes to your Airbyte instance using the octavia apply command. This command will prompt you for validation of the changes. If you want to bypass the validation step, you can use the --force flag. [source](https://docs.airbyte.com/cli-documentation) Here's an example of how the octavia apply command works: bash $ octavia apply 🐙 - weather exists on your Airbyte instance, let's check if we need to update it! 👀 - Here's the computed diff (🚨 remind that diff on secret fields are not displayed): E - Value of root['lat'] changed from "46.7603" to "45.7603". ❓ - Do you want to update weather? [y/N]: y ✍️ - Running update because a diff was detected between local and remote resource. 🎉 - Successfully updated weather on your Airbyte instance! 💾 - New state for weather stored at ./sources/weather/state_<workspace_id>.yaml. [source](https://docs.airbyte.com/cli-documentation) Please note that Octavia will validate the configuration against a JSON schema and will fail to apply the changes if it finds any configuration error. If an error occurs, you will get a stack trace from the API response. [source](https://airbyte.com/tutorials/version-control-airbyte-configurations) Also, after you apply some configuration changes with Octavia, no connection test will be run like when you save connector settings in the UI. You can still use the UI to test that the source setting allows Airbyte to connect. [source](https://airbyte.com/tutorials/version-control-airbyte-configurations)