hey @Artem Astapenko! Updated the UI for the merged Settings / Admin https://www.figma.com/file/etaOkOsnXMoKwbfhCD71kw/Web-app?node-id=21139%3A295

whoa Artem did you do something to the job logs UI? looks very slick now

@Artem Astapenko I've been tracking down a bug that happens when an Airbyte deployment has deprecated connectors and the user clicks on the

update all

button. I believe it's because we delete the deprecated connector from the master list and so the webapp is sending an empty docker tag to the api. More details here. It is possible to work on this today? We have some deprecated connectors been released so this is quite urgent

how can I add a custom connector? There is no option to add one. I am on version

0.27.2-alpha

and started airbyte from scratch

It looks like we always redirect to the main page even if the user navigates to a link that doesn't exists. Is that logic within the web app?

Artem, we set some env vars on the frontend in nginx today. For cloud, we are looking at getting rid of nginx entirely and hoping to just serve the webapp as a static page. Do you know if this is possible/easy to do?

Second question for ya Artem, today when I navigate to

localhost:8000/connections

my browser navigates me to the

connections

tab. How does this work? I'm asking because we are hoping to serve up the webapp (index.html) via CDN for cloud and I want to make sure the routing behaviour is correct

@Artem Astapenko today the webapp sends api request to host it originates from, how easy/difficult would it be to configure it to send request to a separate host? For cloud, we are thinking of serving the webapp on one api and serving the api on another

We already have an issue for it - https://github.com/airbytehq/airbyte/issues/4790 I am working on it now

There is an issue with the urls: Pipedrive and US Census are reversed https://docs.airbyte.io/project-overview/changelog/connectors

@Artem Astapenko looks like the namespace and the stream name is reversed - small bug?

@Artem Astapenko just confirming: is this the new expected format for

anyOf

in specs?

{
  "prop_name": {
    "type": "object",
    "oneOf": [
      {
        "required": ["option_title"],
        "properties": {
          "option_title": {
            "type": "string",
            "constant": "choice_1"
          }
        }
      },
      {
        "required": [
          "option_title",
          "extra_option_1"
        ],
        "properties": {
          "option_title": {
            "type": "string",
            "constant": "choice_2"
          },
          "extra_option_1": {
            // these are just "normal" JSON Schema type definitions, can be integer, object, they can have "description" and "required" fields etc...
            "title": "Extra Option 1",
            "type": "integer"
          }
        }
      }
    ]
  }
}

Hey guys! Not sure this is the right channel for this, but here it goes. When we delete a connection, a source or a destination, the webapp redirects to the previous page, right? For example: if I delete a connection, I'm redirected back to connections page. But the problem is that the page does not update, so I can still see the deleted connection in the list. When I refresh manually, the page renders normally without the deleted connection. You use React, right? It could be a problem with components state updates, maybe.

@Artem Astapenko, I’m working on a new import/export endpoint in the API that is restricted to a specific workspace ID (to select configurations related to the workspace only) Unfortunately I’m encountering problems(/bugs?) with OpenAPI/generator in order to include both a JSON object and a GZIP in the same request body (of an multipart/mixed API endpoint)… WDYT if i split the API into two endpoints instead of a single API (but more complex request body)? • API to upload a GZIP resource file (returns the resourceID being staged for the server) with a gzip request body • API to import the resource file reference by the resourceID into the target WorkspaceID with a json request body

@Artem Astapenko I tagged you for review on a couple of PRs regarding exposing oauth for some connectors: https://github.com/airbytehq/airbyte/pull/5699 Before looking at them it may be helpful to look at this RFC for oauth in cloud

@Artem Astapenko Are we still using the recreate endpoints in the webback-end api? I think these were part of https://github.com/airbytehq/airbyte/pull/471/ to handle clickable source/destination tabs in the onboarding to go back&forth in the flow, right? But then we later on disable those options…

Hi community. We are integrating airbyte into our platform with custom appearance. We are having troubles with some of the sources / destinations definitions that come with

icon: null

at API calls response. Should we then fix it manually? Another pain-point is about denormalized icons measures. Some of these come with similar dimensions, but others are tiny or much bigger than the others. Any tip? Could I help you with it adding icons through Fork - PR?

Hi all, I was wondering whether there are any plans to make the

fields

of streams selectable in the connection settings. I tried to search in Github and Slack for any pointers but could not find any. The idea is that end users can specify which fields they would really need for each stream and this could in turn be used by the connectors to adapt API requests accordingly.

Artem, does the frontend enforce any timeout when calling the api? I’m seeing a 5 min timeout and trying to debug things

Artem, is it possible to have an

https

version of our app locally? some oauth platforms only allow https redirect URLs unfortunately which means local testing is not possible without something like that

Artem, not urgent - when you are up can you take a look at a frontend test? My Airbyte release keeps on erroring out on a front end test (see here, here and here). This ended up passing after I increased the sleep time from the 5 sec default to 10 secs here. Interestingly, only see this happen on the release action (I’ve seen normal builds pass). This passed locally for me everytime I tried to run it (~ 5 times now) The only difference I can see is the node type. The normal builds run on beefier nodes, while the release workflow runs on normal github runners. Curious what you think

Hi, I saw that it is possible to create multiple workspaces through the API. This is very useful for us as can create separate workspaces per customer. What I was wondering, if it is possible to show the workspace name in UI. This would make it more clear to see in which environment you are working.

@Artem Astapenko could you describe what are the key differences of the static content (variables. files, etc.) between envs? (I’m working on task https://github.com/airbytehq/airbyte-cloud/issues/755)

Octavia SVGs for empty states? design is ready for validation! Frontend engineers: Please review the design and acknowledge that you did by replying to this message.

Is there where I would ask questions about the web interface? My question is - does anyone have some kind of authentication proxy that they deploy with the web interface? Currently we use port-forwarding but that means basically granting access to our ops environment and we want to separate those two things

Received a Request to Archive This Channel.

Are we Ready?

Its being Archived in 3…

2…

1…