Skip to content

feat: Add generic database connection mechanism#1163

Open
sbernauer wants to merge 21 commits intomainfrom
spike/generic-databases
Open

feat: Add generic database connection mechanism#1163
sbernauer wants to merge 21 commits intomainfrom
spike/generic-databases

Conversation

@sbernauer
Copy link
Member

@sbernauer sbernauer commented Mar 2, 2026

Description

Part of stackabletech/issues#238

Definition of Done Checklist

  • Not all of these items are applicable to all PRs, the author should update this template to only leave the boxes in that are relevant
  • Please make sure all these things are done and tick the boxes

Author

  • Changes are OpenShift compatible
  • CRD changes approved
  • CRD documentation for all fields, following the style guide.
  • Integration tests passed (for non trivial changes)
  • Changes need to be "offline" compatible

Reviewer

  • Code contains useful comments
  • Code contains useful logging statements
  • (Integration-)Test cases added
  • Documentation added or updated. Follows the style guide.
  • Changelog updated
  • Cargo.toml only contains references to git tags (not specific commits or branches)

Acceptance

  • Feature Tracker has been updated
  • Proper release label has been added

@sbernauer sbernauer marked this pull request as ready for review March 4, 2026 14:23
#[derive(Clone, Debug, Deserialize, JsonSchema, PartialEq, Serialize)]
#[serde(rename_all = "camelCase")]
pub struct GenericCeleryDatabaseConnection {
/// The name of the Secret that contains an `uri` key with the complete SQLAlchemy URI.
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copied over from https://github.com/stackabletech/airflow-operator/pull/743/changes#r2786318061:

I feel URI is very generic. I think connectionString is a better description?

/// Returns the JDBC connection details for the given `unique_database_name` using the
/// default [`TemplatingMechanism`].
///
/// `unique_database_name` identifies this particular database connection within the operator
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

marker: Improve docs a bit on avoiding clashing env var names

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant