Octavia get/import connection is completely broken

Connector Questions & Issues
1
  • Is this your first time deploying Airbyte?: No
  • OS Version / Instance: MacOS
  • Memory / Disk: 4Gb / 1 Tb
  • Deployment: Docker
  • Airbyte Version: 0.42.0
  • Source name/version: n/a
  • Destination name/version: n/a
  • Step: octavia import connection or octavia get connection is broken
  • Description: Octavia CLi is completely broken

It seems that the Octavia CLI is completely inoperable when it comes to working with connections. I filed this Github Issue two weeks ago, but there have been zero comments. I thought I try here, though I’ve asked a bunch of questions in the last week, zero of which have had any response.

It appears that the Octavia CLI is fundamentally broken when it comes to getting or importing connections. This seems like basic functionality to me - set up your connection through a friendly UI, then import the configuration via the CLI. There is an example .zip file in the github issue. Is there anyone in this community that can help or at least respond?

Traceback (most recent call last):
  File "/usr/local/bin/octavia", line 8, in <module>
    sys.exit(octavia())
  File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1128, in __call__
🐙 - Octavia is targetting your Airbyte instance running at http://localhost:8000 on workspace 4f91da45-79b2-402d-875e-08aac8ae36fa.
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1053, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1659, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1659, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib/python3.9/site-packages/octavia_cli/base_commands.py", line 54, in invoke
    raise e
  File "/usr/local/lib/python3.9/site-packages/octavia_cli/base_commands.py", line 51, in invoke
    result = super().invoke(ctx)
  File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1395, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python3.9/site-packages/click/core.py", line 754, in invoke
    return __callback(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/click/decorators.py", line 26, in new_func
    return f(get_current_context(), *args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/octavia_cli/check_context.py", line 91, in wrapper
    f(ctx, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/octavia_cli/_import/commands.py", line 156, in connection
    click.echo(import_connection(ctx.obj["API_CLIENT"], ctx.obj["WORKSPACE_ID"], resource))
  File "/usr/local/lib/python3.9/site-packages/octavia_cli/_import/commands.py", line 87, in import_connection
    remote_configuration = json.loads(get_json_representation(api_client, workspace_id, UnmanagedConnection, resource_to_get))
  File "/usr/local/lib/python3.9/site-packages/octavia_cli/get/commands.py", line 67, in get_json_representation
    return resource.to_json()
  File "/usr/local/lib/python3.9/site-packages/octavia_cli/get/resources.py", line 148, in to_json
    return json.dumps(self.get_remote_resource().to_dict())
  File "/usr/local/lib/python3.9/site-packages/octavia_cli/get/resources.py", line 140, in get_remote_resource
    return self._find_by_resource_name()
  File "/usr/local/lib/python3.9/site-packages/octavia_cli/get/resources.py", line 108, in _find_by_resource_name
    api_response = self._list_for_workspace_fn(self.api_instance, self.list_for_workspace_payload)
  File "/usr/local/lib/python3.9/site-packages/airbyte_api_client/api/web_backend_api.py", line 844, in web_backend_list_connections_for_workspace
    return self.web_backend_list_connections_for_workspace_endpoint.call_with_http_info(**kwargs)
  File "/usr/local/lib/python3.9/site-packages/airbyte_api_client/api_client.py", line 829, in call_with_http_info
    self.__validate_inputs(kwargs)
  File "/usr/local/lib/python3.9/site-packages/airbyte_api_client/api_client.py", line 723, in __validate_inputs
    fixed_val = validate_and_convert_types(
  File "/usr/local/lib/python3.9/site-packages/airbyte_api_client/model_utils.py", line 1570, in validate_and_convert_types
    converted_instance = attempt_convert_item(
  File "/usr/local/lib/python3.9/site-packages/airbyte_api_client/model_utils.py", line 1449, in attempt_convert_item
    raise get_type_error(input_value, path_to_item, valid_classes,
airbyte_api_client.exceptions.ApiTypeError: Invalid type for variable 'web_backend_connection_list_request_body'. Required value type is WebBackendConnectionListRequestBody and passed type was WorkspaceIdRequestBody at ['web_backend_connection_list_request_body']
2

Note that importing by ID instead of name seems to work, so there’s at least a workaround.

3

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.
Best,
The Community Assistance Team