so yeah. i think i'm agreeing what you said at the end artem. if

sourceDefinedCursor=true

then we should not show radio buttons for cursor field.

@Artem Astapenko seems https://github.com/airbytehq/airbyte/pull/2614 is ready? let me know when we merge as https://github.com/airbytehq/airbyte/pull/2460 should be merged right after Thanks!

What can be the cause of that?

Hi @Artem Astapenko I submitted a PR and a question for you to wrap-up the work on the destination sync modes from last week: https://github.com/airbytehq/airbyte/pull/2668#issuecomment-810333765

Hi there, Firefox seems a bit unhappy with the positioning of the Font Awesome check boxes - see attached. Firefox 88.0. Fine in Chrome

@Artem Astapenko & @Mason Wheeler Hadn't gotten a chance until now to appreciate the new connector icons. They look really slick. Nice work.

@Artem Astapenko it looks like master build is failing frontend e2e tests. Mind taking a look when you get a chance?

@Artem Astapenko the little icons are not rendering for me correctly in the drop down menu. is it me or it this an actual bug?

Guys, we used to have link here to 

<https://docs.airbyte.io/>

. Does anybody remember why did we get rid of it? Should revert changes? Or we do not need that logic anymore? Currently it is commented out.

is only with me this happen? adding a source => add destination (should finish the new connection) but come back to add a new dest...

Guys, I have noticed 1 thing and I am not sure whether its correct behaviour or not: When we have an already connection set up, and I try to update it by unselecting some streams by setting

selected

to false - they are never returned from API again. Is it an expected flow or not? So as soon as I have unselected everything - I am not able to select fields again.

I am not able to select the sync type for tables. Airbyte version 0.25.0

Not sure if @Natalie noted this in the onboarding, but it’s still possible to get stuck if something goes wrong, right? I can’t skip onboarding anymore or go back to change my source/destination settings

has the idea of bulk updates been brought up already and discarded? https://github.com/airbytehq/airbyte/issues/4226 just wondering if there is already a priority on this. If not, I think it would be really high UX value for users.

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…