# US 12,112,216 B2 · Declarative API for managing connectors and schemas > Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt - Number: US 12,112,216 B2 - Document ID: US12112216B2 - Status: Granted - Kind: B2 - Application number: 18/046,119 - Filed: 2022-10-12 - Published: 2024-04-18 - Granted: 2024-10-08 - Earliest claimed: 2022-10-12 - Assignees: Confluent, Inc. - Applicants: Confluent, Inc. - Inventors: Rajesh Rc; Pei Yang; Andrew Ding; Rohit Bakhshi; Lokesh Shekar; Steven Costa - Web page: https://patentgrep.com/patent/US12112216B2 ## CPC - G06F 9/5077: {Logical partitioning of resources; Management or configuration of virtualized resources (specific details on emulation or internal functioning of virtual machines G06F9/455)} - G06F 9/547: {Remote procedure calls [RPC]; Web services} - G06F 9/44505: {Configuring for program initiating, e.g. using registry, configuration files} - G06F 9/5072: {Grid computing} - G06F 9/541: {via adapters, e.g. between incompatible applications} - G06F 9/542: {Event management; Broadcasting; Multicasting; Notifications} - H04L 67/02: based on web technology, e.g. hypertext transfer protocol [HTTP] - G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N) - H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M) ## Abstract A request to configure a connect cluster including one or more connectors for a cloud computing system is received. The request include a desired connector state. A connector specification file is automatically generated based on the desired connector state for the connect cluster via a declarative application programming interface (API). Application resources associated with the connect cluster are automatically configured based on the specification file. ## Claims ### Claim 1 A method comprising: receiving, at a declarative application programming interface (API), a request to configure a connect cluster comprising one or more connectors for a cloud computing system, the request including a particular state and a schema defined by a user for the connect cluster; in response to receiving the request, automatically generating a connector specification file based on the particular state and schema defined by the user that triggers installation of one or more connector plugins, the connector specification file including a list of the one or more connector plugins; automatically configuring application resources associated with the connect cluster based on the connector specification file, the automatically configuring including causing download and installation of the one or more connector plugins; detecting a connector in the connect cluster being in a failed state; and in response to detecting the connector being in the failed state, attempting to restart the connector via the declarative API. ### Claim 2 (depends on 1) The method of claim 1, wherein automatically configuring the application resources comprises automatically assigning one or more tasks based on the particular state of the connect cluster specified by the request. ### Claim 3 (depends on 1) The method of claim 1, wherein attempting to restart the connector is based on user input to configure the declarative API to automatically perform a restart attempt. ### Claim 4 (depends on 1) The method of claim 1, further comprising: determining the connector remains in the failed state; and in response to the determining that the connector remains in the failed state, repeatedly attempting to restart the connector until a specified number of restart attempts have been attempted. ### Claim 5 (depends on 1) The method of claim 1, wherein each connector of the one or more connectors comprises: a connector plugin configured to implement one or more classes and one or more abstractions of the connector, and a connector instance configured to manage replication of data between two or more data systems within the cloud computing system. ### Claim 6 (depends on 1) The method of claim 1, wherein the connector specification file further comprises an indication of a maximum amount of volume for storing the one or more connector plugins. ### Claim 7 (depends on 1) The method of claim 1, wherein the connect cluster comprises a plurality of stateful sets, each stateful set of the plurality of stateful sets having a plurality of pods associated therewith. ### Claim 8 (depends on 7) The method of claim 7, wherein the one or more connector plugins are downloaded and installed by an init container in a pod of the plurality of pods, the init container downloading the one or more connector plugins, storing the one or more connector plugins in a node volume, and installing the one or more connector plugins before an application container in the pod runs. ### Claim 9 (depends on 7) The method of claim 7, wherein: the connector specification file further includes a secret name; and the automatically configuring the application resources further comprises injecting data of a secret associated with the secret name into a pod of the plurality of pods. ### Claim 10 (depends on 9) The method of claim 9, wherein the secret comprises one or more of a username, a password, a token, or a key. ### Claim 11 (depends on 7) The method of claim 7, further comprising mounting a certificate in a pod of the plurality of pods based on the particular state, the certificate used by a corresponding connector to securely communicate with an external data system. ### Claim 12 (depends on 1) The method of claim 1, wherein attempting to restart the connector is performed in response to user input indicative of a specified time to trigger a restart attempt. ### Claim 13 A system, comprising: at least one processor; and memory storing instructions that, when executed by the at least one processor cause the system to perform operations comprising: receiving, at a declarative application programming interface (API), a request to configure a connect cluster comprising one or more connectors for a cloud computing system, the request including a particular state and a schema defined by a user for the connect cluster; in response to receiving the request, automatically generating a connector specification file based on the particular state and schema defined by the user that triggers installation of one or more connector plugins, the connector specification file including a list of the one or more connector plugins; automatically configuring application resources associated with the connect cluster based on the connector specification file, the automatically configuring including causing download and installation of the one or more connector plugins; detecting a connector in the connect cluster being in a failed state; and in response to detecting the connector being in the failed state, attempting to restart the connector via the declarative API. ### Claim 14 (depends on 13) The system of claim 13, wherein automatically configuring the application resources comprises automatically assigning one or more tasks based on the particular state of the connect cluster specified by the request. ### Claim 15 (depends on 13) The system of claim 13, wherein attempting to restart the connector is based on user input to configure the declarative API to automatically perform a restart attempt. ### Claim 16 (depends on 13) The system of claim 13, wherein the operations further comprise: determining the connector remains in the failed state; and in response to the determining that the connector remains in the failed state, attempting to restart the connector until a specified number of restart attempts have been attempted. ### Claim 17 (depends on 13) The system of claim 13, wherein each connector of the one or more connectors comprises: a connector plugin configured to implement one or more classes and one or more abstractions of the connector, and a connector instance configured to manage replication of data between two or more data systems within the cloud computing system. ### Claim 18 (depends on 13) The system of claim 13, wherein the connect cluster comprises a plurality of stateful sets, each stateful set of the plurality of stateful sets having a plurality of pods associated therewith. ### Claim 19 (depends on 13) The system of claim 13, wherein attempting to restart the connector is performed in response to user input indicative of a specified time to trigger a restart attempt. ### Claim 20 A non-transitory machine-readable medium having instructions embodied thereon, the instructions executable by a processor of a machine to perform operations comprising: receiving, at a declarative application programming interface (API), a request to configure a connect cluster comprising one or more connectors for a cloud computing system, the request including a particular state and a schema defined by a user for the connect cluster; in response to receiving the request, automatically generating a connector specification file based on the particular state and schema defined by the user that triggers installation of one or more connector plugins, the connector specification file including a list of the one or more connector plugins; automatically configuring application resources associated with the connect cluster based on the specification file, the automatically configuring including causing download and installation of the one or more connector plugins; detecting a connector in the connect cluster being in a failed state; and in response to detecting the connector being in the failed state, attempting to restart the connector via the declarative API.