I have imported my connections from the older vers...
# replication-ask-ai
h
I have imported my connections from the older version of airbyte and trying to apply to new airbyte instance on kubernetes engine deployed with helm chart. I get the following error:
Copy code
airbyte_api_client.exceptions.ApiTypeError: Invalid type for variable 'non_breaking_changes_preference'. Required value type is NonBreakingChangesPreference and passed type was str at ['non_breaking_changes_preference']
What can be the reason?
k
A message from kapa.ai
The error message you're seeing is related to the
non_breaking_changes_preference
variable in your connection configuration. This error typically occurs when the type of the variable in the configuration does not match the expected type. In this case, the
non_breaking_changes_preference
variable is expected to be of type
NonBreakingChangesPreference
, but a string (
str
) was provided instead. This issue has been reported by several users when using the
octavia apply
command to import connections into a new Airbyte instance. It seems to be a compatibility issue between different versions of Airbyte and Octavia. One workaround that has been suggested is to remove the keys causing the issue from the
connections.yaml
file before applying the import. However, this might not be the best solution as it involves manually editing the configuration file. Another solution is to ensure that the versions of Airbyte and Octavia you're using are compatible. Some users have reported that the issue was resolved when they updated both Airbyte and Octavia to the latest versions. If you're still facing the issue, I recommend following the ongoing discussions on the [Airbyte Slack](https://airbytehq.slack.com/archives/C021JANJ6TY/p1671822414723089) and [Airbyte Forum](https://discuss.airbyte.io/t/3145) for any updates or potential fixes.
h
i use airbyte 0.50.5 and airbyte/octavia-cli:0.44.4 what is the compatible octavia version that i should use? @kapa.ai
k
A message from kapa.ai
You should install the same Octavia version as the targeted Airbyte instance to avoid API incompatibility issues. Therefore, if you're using Airbyte 0.50.5, you should use the same version for Octavia CLI. You can install the latest Octavia version as a bash command using the following code:
Copy code
bash curl -s -o- <https://raw.githubusercontent.com/airbytehq/airbyte/master/octavia-cli/install.sh> | bash
This will add the Octavia alias to your bash profile and create an
.octavia
file where you can configure environment variables and secrets. For more details, you can check the [Octavia CLI documentation](https://github.com/airbytehq/airbyte/blob/master/octavia-cli/README.md#install) and the [tutorial on version control Airbyte configurations with Octavia CLI](https://airbyte.com/tutorials/version-control-airbyte-configurations). Source: [Airbyte Tutorials](https://airbyte.com/tutorials/version-control-airbyte-configurations)
h
there is no such version for octavia 0.50.5 i got this error: : manifest for airbyte/octavia-cli:0.50.0 not found: manifest unknown: manifest unknown. @kapa.ai
k
A message from kapa.ai
I apologize for the confusion. It seems there was a misunderstanding. The Octavia CLI version does not necessarily match the Airbyte version. In a previous support conversation, a user resolved a similar issue by ensuring that the Octavia version was compatible with their Airbyte version. However, the exact version numbers were not specified. I recommend reaching out to the Airbyte support team directly or posting your question on the Airbyte community Slack or forum for a more accurate answer. Source: [Airbyte Slack Support Conversation](https://airbytehq.slack.com/archives/C021JANJ6TY/p1670864305550559)
h
i used the workaround that has been suggested is to remove the keys causing the issue from the
connections.yaml
worked for me
s
@Haki Dere where was the connections.yaml file stored?
h
you get configs for your connections sources or destinations with octavia. do you have octavia installed?
Like this :
octavia  --airbyte-url <YOUR_AIRBYTE_HOSTNAME> import connections
This will create the following folder structure in the current working directory as follow: • connections |--- name_of_the_connection |---
configurations.yaml
• sources • destinations
configurations.yaml is the file you should modify and remove the
non_breaking_changes_preference
and so on
not the best way but works
s
This is helpful. After making changes, how do we push/export the changes?
h
octavia  --airbyte-url <YOUR_NEW_AIRBYTE_HOSTNAME> apply
thanku 1