BREAKING CHANGE: Deprecating Security Insights

.bumpversion.cfg

@@ -19,10 +19,6 @@ replace = {new_version}
 search = {current_version}
 replace = {new_version}
 
-[bumpversion:file:modules/findings/pom.xml]
-search = {current_version}
-replace = {new_version}
-
 [bumpversion:file:modules/configuration-governance/pom.xml]
 search = {current_version}
 replace = {new_version}

.github/workflows/main.yaml

@@ -47,7 +47,6 @@ jobs:
       - name: running integration tests
         env:
           ACCOUNT_ID: ${{ secrets.ACCOUNT_ID }}
-          FINDINGS_ENV: ${{ secrets.FINDINGS_ENV }}
           CONFIGURATION_GOVERNANCE_ENV: ${{ secrets.CONFIGURATION_GOVERNANCE_ENV }}
           RESOURCE_GROUP_ID: ${{ secrets.RESOURCE_GROUP_ID }}
         run: build/testScript.sh

README.md

@@ -46,7 +46,6 @@ The IBM Cloud Security & Compliance Center Java SDK allows developers to program
 
 Service Name | Imported Class Name
 --- | ---
-[FindingsApi](https://cloud.ibm.com/apidocs/security-compliance/findings) | FindingsApi:2.0.1
 [ConfigurationGovernanceApi](https://cloud.ibm.com/apidocs/security-compliance/config) | ConfigurationGovernanceApi:2.0.1
 
 ## Prerequisites
@@ -76,14 +75,14 @@ Here are examples for maven and gradle:
 ```xml
 <dependency>
     <groupId>com.ibm.cloud</groupId>
-    <artifactId>findings</artifactId>
+    <artifactId>configuration_governance</artifactId>
     <version>2.0.1</version>
 </dependency>
 ```
 
 ### Gradle
 ```gradle
-compile 'com.ibm.cloud:findings:2.0.1'
+compile 'com.ibm.cloud:configuration_governance:2.0.1'
 ```
 
 ## Using the SDK

build/publishCodeCoverage.sh

@@ -7,8 +7,7 @@ printf ">>>>> Publishing code coverage info\n"
 
 JACOCO_SOURCE_PATH=modules/common/src/main/java ./cc-test-reporter format-coverage modules/common/target/site/jacoco/jacoco.xml -d -o common.json -t jacoco
 JACOCO_SOURCE_PATH=modules/configuration-governance/src/main/java ./cc-test-reporter format-coverage modules/configuration-governance/target/site/jacoco/jacoco.xml -d -o configuration-governance.json -t jacoco
-JACOCO_SOURCE_PATH=modules/findings/src/main/java ./cc-test-reporter format-coverage modules/findings/target/site/jacoco/jacoco.xml -d -o findings.json -t jacoco
 
-./cc-test-reporter sum-coverage common.json configuration-governance.json findings.json -o coverage.json -d
+./cc-test-reporter sum-coverage common.json configuration-governance.json -o coverage.json -d
 
 ./cc-test-reporter upload-coverage --input coverage.json

build/testScript.sh

@@ -3,6 +3,5 @@
 set -euo pipefail
 
 curl https://us-south.functions.appdomain.cloud/api/v1/web/e6b54af6-ab44-4149-a8e4-e906dcc58136/default/secadvstg-location-shift.json
-echo "${FINDINGS_ENV}" | base64 -d >> findings_v1.env
 echo "${CONFIGURATION_GOVERNANCE_ENV}" | base64 -d >> configuration_governance_v1.env
 mvn clean verify

modules/coverage-reports/pom.xml

@@ -38,11 +38,6 @@
         </dependency>
 
         <!-- Copy and update this section for each service added to the project. -->
-        <dependency>
-            <groupId>${project.groupId}</groupId>
-            <artifactId>findings</artifactId>
-            <version>${project.version}</version>
-        </dependency>
 
         <dependency>
             <groupId>${project.groupId}</groupId>

modules/examples/pom.xml

@@ -17,11 +17,6 @@
         <!-- There should be a dependency for each module whose request example class exists in this "examples" module. Add 
             new "dependency" entries here as needed when you add a request examples class for a new service. Note: the "artifactId" values 
             below should reflect the "artifactId" value specified in each module's pom.xml file (i.e. not the module's directory name). -->
-        <dependency>
-            <groupId>com.ibm.cloud</groupId>
-            <artifactId>findings</artifactId>
-            <version>${project.version}</version>
-        </dependency>
         <dependency>
             <groupId>com.ibm.cloud</groupId>
             <artifactId>configuration_governance</artifactId>