chore(cloud-native)!: remove spanner support from OCI images

[iromli]

Prepare

• Read PR guidelines
• Read license information

---

Description

Target issue

closes #10046

Implementation Details

---

Test and Document the changes

• Static code analysis has been run locally and issues have been fixed
• Relevant unit and integration tests have been added/updated
• Relevant documentation has been updated if any (i.e. user guides, installation and configuration guides, technical design docs etc)

Please check the below before submitting your PR. The PR will not be merged if there are no commits that start with docs: to indicate documentation changes or if the below checklist is not selected.

• I confirm that there is no impact on the docs due to the code changes in this PR.

[dryrunsecurity]

DryRun Security Summary

The provided code changes focus on the removal of support for the Google Spanner persistence backend across various components of the Janssen project, simplifying the persistence layer and improving the overall security posture of the application.

Expand for full summary

Summary:

The provided code changes focus on the removal of support for the Google Spanner persistence backend across various components of the Janssen project. This simplification of the persistence layer is a positive security change, as it reduces the attack surface and complexity of the application. The changes also include updates to the configuration, client scopes, and logging for the Janssen Auth Server, Casa, and Config API applications, further improving the overall security posture of the project.

While the changes do not appear to introduce any immediate security vulnerabilities, it is essential to thoroughly review the updated configurations, dependencies, and persistence layer integrations to ensure that the application's security is not compromised. Factors such as secure credential management, input validation, and monitoring should be carefully evaluated to maintain the overall security of the Janssen project.

Files Changed:

1. Requirements.txt: The google-cloud-spanner dependency has been removed, and the couchbase dependency has been added, indicating a shift in the project's persistence backend.
2. Dockerfile: The environment variables related to Google Spanner have been removed, and the configuration has been updated to focus on Couchbase and SQL as the supported persistence types.
3. Bootstrap.py: The code that handled the Spanner persistence backend has been removed, simplifying the application's setup and reducing the attack surface.
4. Upgrade.py: The code changes focus on updating the client scopes, configurations, and persistence layer integrations to ensure a smooth upgrade process.
5. mod_context.py: The changes remove the Spanner-related functionality and focus on managing the Couchbase persistence layer dependencies.
6. README.md: The documentation has been updated to reflect the removal of the Spanner persistence type and the changes to the supported persistence configurations.

Code Analysis

We ran 9 analyzers against 30 files and 1 analyzer had findings. 8 analyzers had no findings.

Analyzer	Findings
Sensitive Files Analyzer	5 findings

Riskiness

🟢 Risk threshold not exceeded.

View PR in the DryRun Dashboard.

[iromli]

Superseded by #10070