Unable to Apply Airbyte Configuration using OCTAVIA CLI

  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: Ubuntu
  • Memory / Disk: you can use something like 16 Gb / 1 Tb
  • Deployment: Are you using Docker
  • Airbyte Version: 0.42.0
  • Source name/version: Chargebee
  • Destination name/version: S3
  • Step: Apply configuration through OCTAVIA-CLI
  • Description: I am using airbyte 0.42.0 and octavia 0.41.1, when importing my airbyte source destinaion using octavia its working fine but while applying it creates source and destination correctly but not able to create connection, getting below error

raise get_type_error(input_value, path_to_item, valid_classes,
*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’]

This seems to be a known issue, but no indication of root cause or path to fix:

If you import a source, it will add some fields that then can’t be sent back. If you delete the fields from your configuration, it will select the defaults (though it will prompt you each time if you don’t use --force). If you need something other than the defaults, then I think you’re out of luck.

Thanks for the response.
I am using these values for mentioned parameters
schema_change: no_change
notify_schema_changes: false
non_breaking_changes_preference: ignore
namespace_definition: destination

Hello there! You are receiving this message because none of your fellow community members has stepped in to respond to your topic post. (If you are a community member and you are reading this response, feel free to jump in if you have the answer!) As a result, the Community Assistance Team has been made aware of this topic and will be investigating and responding as quickly as possible.
Some important considerations that will help your to get your issue solved faster:

  • It is best to use our topic creation template; if you haven’t yet, we recommend posting a followup with the requested information. With that information the team will be able to more quickly search for similar issues with connectors and the platform and troubleshoot more quickly your specific question or problem.
  • Make sure to upload the complete log file; a common investigation roadblock is that sometimes the error for the issue happens well before the problem is surfaced to the user, and so having the tail of the log is less useful than having the whole log to scan through.
  • Be as descriptive and specific as possible; when investigating it is extremely valuable to know what steps were taken to encounter the issue, what version of connector / platform / Java / Python / docker / k8s was used, etc. The more context supplied, the quicker the investigation can start on your topic and the faster we can drive towards an answer.
  • We in the Community Assistance Team are glad you’ve made yourself part of our community, and we’ll do our best to answer your questions and resolve the problems as quickly as possible. Expect to hear from a specific team member as soon as possible.

Thank you for your time and attention.
The Community Assistance Team

Hey @Avi, I see you’ve started a thread here in Slack:

Is this the same issue?