connectors | product designed and developed by the company Filigran | Security library

We are developing a MS Teams application (using incoming webhooks to deliver messages from our SaaS app into Teams) and have noticed that when creating new connectors using the MS Connectors Developer Dashboard (https://outlook.office.com/connectors/publish) the connector install process no longer functions as it used to.

Up until about a week ago, the connector install process involved the connector configuration page being loaded as an iframe within the teams app install modal. This is exactly as described and expected in the MS docs here: https://docs.microsoft.com/en-us/microsoftteams/platform/webhooks-and-connectors/how-to/connectors-creating

This install process should look like this: Working connector

Currently, when creating connectors, the resulting install flow looks like this. (Notice how it no longer renders configuration screen in iframe, but instead links to it): Broken connector

I have diff'ed the application manifest and confirmed the only difference in setup is the connector ID. I've also double checked that all the connector fields (valid domains, configuration URLs etc.) are exactly as before. The change seems to be on Microsoft side. My old connectors created earlier this month continue to work OK

My question is, what is this new install flow that I'm seeing and why is it suddenly showing up now? How can I tell Teams to go back to using the old install flow for my new connectors.

Other details that may be relevant:

• I've tried creating connectors in two separate MS Office accounts, both work the same way
• The app is NOT yet published, I'm testing locally by uploading and approving within our company's Teams account
• I've confirmed the configuration endpoint is viewable from the outside world and have found now network errors in the teams app that would explain it failing to load.

Trying to make my own component based on KubernetesPodOperator. I am able to define and add the component to the list of components but when trying to run it, I get:

Operator 'KubernetesPodOperator' of node 'KubernetesPodOperator' is not configured in the list of available operators. Please add the fully-qualified package name for 'KubernetesPodOperator' to the AirflowPipelineProcessor.available_airflow_operators configuration.

and error:

We have an Microsoft Search instance for crawling one custom app : https://docs.microsoft.com/en-us/microsoftsearch/connectors-overview

Query & display is working as expected but aggregation provides wrong results

query JSON : https://graph.microsoft.com/v1.0/search/query

select title + submitter and aggregation on submitter

I'm creating a Dataproc cluster, and it is timing out when i'm adding the connectors.sh in the initialization actions.

here is the command & error

We use to spin cluster with below configurations. It used to run fine till last week but now failing with error ERROR: Failed cleaning build dir for libcst Failed to build libcst ERROR: Could not build wheels for libcst which use PEP 517 and cannot be installed directly

I'm trying to migrate from airflow 1.10 to Airflow 2 which has a change of name for some operators which includes - DataprocClusterCreateOperator. Here is an extract of the code.

Do we have any system tables in Snowflake which gives us the credit usage information like : a. Warehouse level b. Account level, etc..

Requirement --> We have a requirement where there is a need to extract those information from SF via available SF connectors & orchestrate them as per the need of the client.

Regards, Somen Swain

We have set our Kafka Connect to be able to read credentials from a file, instead of giving them directly in connector config. This is how a login part of connector config looks like:

"connection.user": "${file:/kafka/pass.properties:username}",

"connection.password": "${file:/kafka/pass.properties:password}",

We also added these 2 lines to "connect-distributed.properties" file:

config.providers=file

config.providers.file.class=org.apache.kafka.common.config.provider.FileConfigProvider

Mind that it works perfectly for JDBC connectors, so there is no problem with the pass.properties file. But for other connectors, such as couchbase, rabbitmq, s3 etc. it causes problems. All these connectors work fine when we give credentials directly but when we try to make Connect to read them from a file it gives some errors. What could be the reason? I don't see any JDBC specific configuration here.

EDIT:

An error about couchbase in connect.log:

I would like to add real time data from SQL server to Kafka directly and I found there is a SQL server connector provided by https://debezium.io/docs/connectors/sqlserver/

In the documentation, it says that it will create one topic for each table. I am trying to understand the architecture because I have 500 clients which means I have 500 databases and each of them has 500 tables. Does it mean that it will create 250000 topics or do I need separate Kafka Cluster for each client and each cluster/node will have 500 topics based on the number of tables in the database?

Is it the best way to send SQL data to Kafka or should we send an event to Kafka queue through code whenever there is an insert/update/delete on a table?