PromucFlow_constructor/app/server/appsmith-interfaces/pom.xml

257 lines
8.8 KiB
XML
Raw Normal View History

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd">
<modelVersion>4.0.0</modelVersion>
<parent>
<groupId>com.appsmith</groupId>
<artifactId>integrated</artifactId>
<version>1.0-SNAPSHOT</version>
</parent>
<artifactId>interfaces</artifactId>
<version>1.0-SNAPSHOT</version>
<name>interfaces</name>
<properties>
<jjwt.version>0.11.5</jjwt.version>
</properties>
<dependencies>
<dependency>
<groupId>com.hierynomus</groupId>
<artifactId>sshj</artifactId>
<version>0.35.0</version>
<exclusions>
<exclusion>
<groupId>org.bouncycastle</groupId>
<artifactId>bcprov-jdk15on</artifactId>
</exclusion>
</exclusions>
</dependency>
<!-- Actual Junit5 implementation. Will transitively include junit-jupiter-api -->
<dependency>
<groupId>org.junit.jupiter</groupId>
<artifactId>junit-jupiter-engine</artifactId>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.junit.platform</groupId>
<artifactId>junit-platform-suite-engine</artifactId>
<scope>test</scope>
</dependency>
<!-- For junit5 parameterised test support -->
<dependency>
<groupId>org.junit.jupiter</groupId>
<artifactId>junit-jupiter-params</artifactId>
<scope>test</scope>
</dependency>
<!-- Only required to run junit5 test from IDE -->
<dependency>
<groupId>org.junit.platform</groupId>
<artifactId>junit-platform-launcher</artifactId>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.pf4j</groupId>
<artifactId>pf4j</artifactId>
<version>${org.pf4j.version}</version>
</dependency>
<dependency>
<groupId>org.springframework.data</groupId>
<artifactId>spring-data-mongodb</artifactId>
<version>4.0.0</version>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>org.springframework.boot</groupId>
<artifactId>spring-boot-starter-data-mongodb-reactive</artifactId>
</dependency>
<dependency>
<groupId>org.json</groupId>
<artifactId>json</artifactId>
<version>20231013</version>
</dependency>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-web</artifactId>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>org.projectlombok</groupId>
<artifactId>lombok</artifactId>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>com.fasterxml.jackson.core</groupId>
<artifactId>jackson-databind</artifactId>
<version>${jackson-bom.version}</version>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>com.fasterxml.jackson.datatype</groupId>
<artifactId>jackson-datatype-jsr310</artifactId>
<version>${jackson-bom.version}</version>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>com.google.code.gson</groupId>
<artifactId>gson</artifactId>
</dependency>
Support Prepared Statements in Postgres (#2967) * Pushing minor editor form changes to ensure that prepared statement could be turned off. * Code refactor to do variable substitution in PluginExecutor instead of action service. * WIP : Prepared Statement handling in psql plugin * WIP Prepared Statements. * Working version of prepared statements * Quote trimming added for post preparing sql statements. Now the unprepared statements and prepared statements do not require edits. * Fixed existing test cases failing. * Code formatting. * Super minor code cleanup. * Added migration for the existing postgres actions. * Fixed failing test cases in ActionServiceTest. * Minor change in the text for turning on and off prepared statements in the postgres query pane. * Added test cases for prepared statement. * Some minor comments for code readability * Moved Prepared Statement setting from Action Configuration to Plugin Specified Templates since this setting does not make sense for all the DB plugins. * Added function level comments * Update app/server/appsmith-interfaces/src/main/java/com/appsmith/external/helpers/SqlStringUtils.java Co-authored-by: Arpit Mohan <mohanarpit@users.noreply.github.com> * Update app/server/appsmith-interfaces/src/main/java/com/appsmith/external/helpers/SqlStringUtils.java Co-authored-by: Arpit Mohan <mohanarpit@users.noreply.github.com> * Incorporated review comments. * Fixed compile time error. Co-authored-by: Arpit Mohan <mohanarpit@users.noreply.github.com>
2021-02-18 13:03:27 +00:00
<dependency>
<groupId>org.apache.commons</groupId>
<artifactId>commons-text</artifactId>
2022-10-14 14:06:16 +00:00
<version>1.10.0</version>
Support Prepared Statements in Postgres (#2967) * Pushing minor editor form changes to ensure that prepared statement could be turned off. * Code refactor to do variable substitution in PluginExecutor instead of action service. * WIP : Prepared Statement handling in psql plugin * WIP Prepared Statements. * Working version of prepared statements * Quote trimming added for post preparing sql statements. Now the unprepared statements and prepared statements do not require edits. * Fixed existing test cases failing. * Code formatting. * Super minor code cleanup. * Added migration for the existing postgres actions. * Fixed failing test cases in ActionServiceTest. * Minor change in the text for turning on and off prepared statements in the postgres query pane. * Added test cases for prepared statement. * Some minor comments for code readability * Moved Prepared Statement setting from Action Configuration to Plugin Specified Templates since this setting does not make sense for all the DB plugins. * Added function level comments * Update app/server/appsmith-interfaces/src/main/java/com/appsmith/external/helpers/SqlStringUtils.java Co-authored-by: Arpit Mohan <mohanarpit@users.noreply.github.com> * Update app/server/appsmith-interfaces/src/main/java/com/appsmith/external/helpers/SqlStringUtils.java Co-authored-by: Arpit Mohan <mohanarpit@users.noreply.github.com> * Incorporated review comments. * Fixed compile time error. Co-authored-by: Arpit Mohan <mohanarpit@users.noreply.github.com>
2021-02-18 13:03:27 +00:00
<scope>compile</scope>
</dependency>
<dependency>
<groupId>commons-validator</groupId>
<artifactId>commons-validator</artifactId>
<version>1.7</version>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>commons-io</groupId>
<artifactId>commons-io</artifactId>
<version>2.7</version>
Support Prepared Statements in Postgres (#2967) * Pushing minor editor form changes to ensure that prepared statement could be turned off. * Code refactor to do variable substitution in PluginExecutor instead of action service. * WIP : Prepared Statement handling in psql plugin * WIP Prepared Statements. * Working version of prepared statements * Quote trimming added for post preparing sql statements. Now the unprepared statements and prepared statements do not require edits. * Fixed existing test cases failing. * Code formatting. * Super minor code cleanup. * Added migration for the existing postgres actions. * Fixed failing test cases in ActionServiceTest. * Minor change in the text for turning on and off prepared statements in the postgres query pane. * Added test cases for prepared statement. * Some minor comments for code readability * Moved Prepared Statement setting from Action Configuration to Plugin Specified Templates since this setting does not make sense for all the DB plugins. * Added function level comments * Update app/server/appsmith-interfaces/src/main/java/com/appsmith/external/helpers/SqlStringUtils.java Co-authored-by: Arpit Mohan <mohanarpit@users.noreply.github.com> * Update app/server/appsmith-interfaces/src/main/java/com/appsmith/external/helpers/SqlStringUtils.java Co-authored-by: Arpit Mohan <mohanarpit@users.noreply.github.com> * Incorporated review comments. * Fixed compile time error. Co-authored-by: Arpit Mohan <mohanarpit@users.noreply.github.com>
2021-02-18 13:03:27 +00:00
<scope>compile</scope>
</dependency>
<dependency>
<groupId>org.assertj</groupId>
<artifactId>assertj-core</artifactId>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.hibernate.validator</groupId>
<artifactId>hibernate-validator</artifactId>
</dependency>
<dependency>
<groupId>net.minidev</groupId>
<artifactId>json-smart</artifactId>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>org.eclipse.jgit</groupId>
<artifactId>org.eclipse.jgit</artifactId>
<version>6.6.1.202309021850-r</version>
<scope>compile</scope>
</dependency>
<dependency>
<groupId>com.h2database</groupId>
<artifactId>h2</artifactId>
</dependency>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-webflux</artifactId>
</dependency>
<dependency>
<groupId>io.projectreactor.netty</groupId>
<artifactId>reactor-netty-core</artifactId>
<scope>provided</scope>
</dependency>
<dependency>
<groupId>io.projectreactor.netty</groupId>
<artifactId>reactor-netty-http</artifactId>
<exclusions>
<exclusion>
<groupId>io.projectreactor</groupId>
<artifactId>reactor-core</artifactId>
</exclusion>
<exclusion>
<groupId>io.netty</groupId>
<artifactId>netty-resolver-dns-native-macos</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>commons-lang</groupId>
<artifactId>commons-lang</artifactId>
<version>2.6</version>
</dependency>
<dependency>
<groupId>io.jsonwebtoken</groupId>
<artifactId>jjwt-api</artifactId>
<version>${jjwt.version}</version>
</dependency>
<dependency>
<groupId>io.jsonwebtoken</groupId>
<artifactId>jjwt-impl</artifactId>
<version>${jjwt.version}</version>
</dependency>
<dependency>
<groupId>io.jsonwebtoken</groupId>
<artifactId>jjwt-jackson</artifactId>
<!-- or jjwt-gson if Gson is preferred -->
<version>${jjwt.version}</version>
<exclusions>
<exclusion>
<groupId>com.fasterxml.jackson.core</groupId>
<artifactId>*</artifactId>
</exclusion>
</exclusions>
</dependency>
<!--Test dependencies-->
<dependency>
<groupId>io.projectreactor</groupId>
<artifactId>reactor-test</artifactId>
<version>${reactor-test.version}</version>
<scope>test</scope>
</dependency>
<!-- https://mvnrepository.com/artifact/com.squareup.okhttp3/mockwebserver3 -->
<dependency>
<groupId>com.squareup.okhttp3</groupId>
<artifactId>mockwebserver3</artifactId>
<version>${mockwebserver.version}</version>
<scope>test</scope>
<exclusions>
<exclusion>
<groupId>com.squareup.okhttp3</groupId>
<artifactId>okhttp</artifactId>
</exclusion>
</exclusions>
</dependency>
<dependency>
<groupId>com.squareup.okhttp3</groupId>
<artifactId>okhttp</artifactId>
<version>${okhttp3.version}</version>
</dependency>
<dependency>
<groupId>org.mockito</groupId>
<artifactId>mockito-core</artifactId>
<version>${mockito.version}</version>
<scope>test</scope>
</dependency>
<dependency>
<groupId>org.springframework</groupId>
<artifactId>spring-test</artifactId>
<scope>test</scope>
</dependency>
feat: Server side observability (#19828) ## Description TL;DR: This PR introduces metrics logging using native Spring support for Micrometer. It includes a docker-compose to set up all the required parts of this observability stack in the local environment as well. In order to make use of this stack, please navigate to `utils/observability` and execute the following command: ``` docker-compose up -d ``` The set up comes bundled with a default Grafana dashboard that can be accessed at localhost:3001. Please feel free to switch the mapping ports around in the docker-compose file. This dashboard currently shows all http requests (sampled at 0.1 by default), and the server side implementation has introduced some minimal tracing for the `/api/v1/action/execute` endpoint. This means that you can use the trace id from http server requests for this endpoint to delve deeper into the spans exposed in this flow. In case you would like to send trace information to another service, please make use of the `APPSMITH_TRACING_ENDPOINT` variable. To override the default sampling rate in your local (to say, 1), you can set that as the value for the variable `APPSMITH_SAMPLING_PROBABILITY`. Fixes #19153 ## Type of change - Chore (housekeeping or task changes that don't impact user perception) ## How Has This Been Tested? - Manual ### Test Plan No testing required, only needs regression after merge. ## Checklist: ### Dev activity - [x] My code follows the style guidelines of this project - [x] I have performed a self-review of my own code - [x] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [x] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [x] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag --------- Co-authored-by: Sumesh Pradhan <sumesh@appsmith.com>
2023-02-07 08:56:18 +00:00
<dependency>
<groupId>io.projectreactor</groupId>
<artifactId>reactor-core-micrometer</artifactId>
</dependency>
feat: PGSql MTLS support (#31067) ## Description Mutual TLS, or mTLS for short, is a method for mutual authentication. mTLS ensures that the parties at each end of a network connection are who they claim to be by verifying that they both have the correct private key. This PR adds support for mTLS for postgres datasource. Unlike the standard way of storing the certs in disk, we store them in the database. This has been achieved via the custom implementation of SSL Factory. The postgres driver support passing the custom ssl factory while creating connection, which then will be used for handling and establishing the connection. #### PR fixes following issue(s) Fixes #31326 #### Type of change - New feature (non-breaking change which adds functionality) ## Testing #### How Has This Been Tested? - [ ] Manual #### Test Plan > Add Testsmith test cases links that relate to this PR > > #### Issues raised during DP testing > Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR) > > > ## Checklist: #### Dev activity - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced the Postgres plugin to support SSL certificate validation for secure database connections. Users can now select between `VERIFY_CA` and `VERIFY_FULL` modes for SSL verification, ensuring a higher level of security for database communications. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2024-03-04 09:08:27 +00:00
<dependency>
<groupId>org.bouncycastle</groupId>
<artifactId>bcprov-jdk18on</artifactId>
<version>1.78</version>
feat: PGSql MTLS support (#31067) ## Description Mutual TLS, or mTLS for short, is a method for mutual authentication. mTLS ensures that the parties at each end of a network connection are who they claim to be by verifying that they both have the correct private key. This PR adds support for mTLS for postgres datasource. Unlike the standard way of storing the certs in disk, we store them in the database. This has been achieved via the custom implementation of SSL Factory. The postgres driver support passing the custom ssl factory while creating connection, which then will be used for handling and establishing the connection. #### PR fixes following issue(s) Fixes #31326 #### Type of change - New feature (non-breaking change which adds functionality) ## Testing #### How Has This Been Tested? - [ ] Manual #### Test Plan > Add Testsmith test cases links that relate to this PR > > #### Issues raised during DP testing > Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR) > > > ## Checklist: #### Dev activity - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced the Postgres plugin to support SSL certificate validation for secure database connections. Users can now select between `VERIFY_CA` and `VERIFY_FULL` modes for SSL verification, ensuring a higher level of security for database communications. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2024-03-04 09:08:27 +00:00
<scope>compile</scope>
</dependency>
<dependency>
<groupId>io.micrometer</groupId>
<artifactId>micrometer-tracing</artifactId>
</dependency>
feat: PGSql MTLS support (#31067) ## Description Mutual TLS, or mTLS for short, is a method for mutual authentication. mTLS ensures that the parties at each end of a network connection are who they claim to be by verifying that they both have the correct private key. This PR adds support for mTLS for postgres datasource. Unlike the standard way of storing the certs in disk, we store them in the database. This has been achieved via the custom implementation of SSL Factory. The postgres driver support passing the custom ssl factory while creating connection, which then will be used for handling and establishing the connection. #### PR fixes following issue(s) Fixes #31326 #### Type of change - New feature (non-breaking change which adds functionality) ## Testing #### How Has This Been Tested? - [ ] Manual #### Test Plan > Add Testsmith test cases links that relate to this PR > > #### Issues raised during DP testing > Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR) > > > ## Checklist: #### Dev activity - [ ] My code follows the style guidelines of this project - [ ] I have performed a self-review of my own code - [ ] I have commented my code, particularly in hard-to-understand areas - [ ] I have made corresponding changes to the documentation - [ ] My changes generate no new warnings - [ ] I have added tests that prove my fix is effective or that my feature works - [ ] New and existing unit tests pass locally with my changes - [ ] PR is being merged under a feature flag #### QA activity: - [ ] [Speedbreak features](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#speedbreakers-) have been covered - [ ] Test plan covers all impacted features and [areas of interest](https://github.com/appsmithorg/TestSmith/wiki/Guidelines-for-test-plans#areas-of-interest-) - [ ] Test plan has been peer reviewed by project stakeholders and other QA members - [ ] Manually tested functionality on DP - [ ] We had an implementation alignment call with stakeholders post QA Round 2 - [ ] Cypress test cases have been added and approved by SDET/manual QA - [ ] Added `Test Plan Approved` label after Cypress tests were reviewed - [ ] Added `Test Plan Approved` label after JUnit tests were reviewed <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit - **New Features** - Enhanced the Postgres plugin to support SSL certificate validation for secure database connections. Users can now select between `VERIFY_CA` and `VERIFY_FULL` modes for SSL verification, ensuring a higher level of security for database communications. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
2024-03-04 09:08:27 +00:00
</dependencies>
2022-09-19 02:34:30 +00:00
</project>