[ 
https://issues.apache.org/jira/browse/FLINK-40030?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated FLINK-40030:
-----------------------------------
    Labels: pull-request-available  (was: )

> Add architecture tests to flink-connector-http
> ----------------------------------------------
>
>                 Key: FLINK-40030
>                 URL: https://issues.apache.org/jira/browse/FLINK-40030
>             Project: Flink
>          Issue Type: Improvement
>          Components: Connectors / HTTP
>            Reporter: Bharath Reddy Gunapati
>            Priority: Minor
>              Labels: pull-request-available
>
> The HTTP connector currently has no architecture tests, unlike most other
> Flink connectors (e.g. flink-connector-kafka, flink-connector-jdbc,
> flink-connector-aws), which enforce structural rules via the shared
> flink-architecture-tests framework (ArchUnit).
>  
> This issue proposes adding the standard Flink architecture tests to
> flink-connector-http so that the connector is held to the same architectural
> guarantees as the rest of the Flink connector ecosystem, and so that new
> violations are caught automatically in CI.
>  
> Scope:
> * Add the test-scoped flink-architecture-tests-test and
> flink-architecture-tests-production dependencies.
> * Add the standard entry-point test classes under
> org.apache.flink.architecture:
> - ProductionCodeArchitectureTest (DoNotIncludeTests)
> - TestCodeArchitectureTest (OnlyIncludeTests)
> * Add src/test/resources/archunit.properties with the standard freezing-store
> configuration (archRule.failOnEmptyShould=false for rules that do not apply
> to this connector).
> * Commit the initial archunit-violations freezing store as a baseline.
>  
> As is conventional when introducing architecture tests (see FLINK-24138), the
> existing violations are recorded in the frozen baseline rather than fixed in
> this change. This keeps the PR scoped to "add tests only"; the frozen
> violations (e.g. usage of Flink-internal/shaded APIs, and missing 
> @PublicEvolving
> annotations on the connector's own API surface) can be triaged and reduced in
> follow-up issues.
>  
> No production code is changed and no public API is affected. The added
> dependencies are test-only.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to