Skip to content

Feat registry in lakebase#12

Merged
benoitcayladbx merged 8 commits into
developfrom
FEAT_RegistryInLakebase
Apr 29, 2026
Merged

Feat registry in lakebase#12
benoitcayladbx merged 8 commits into
developfrom
FEAT_RegistryInLakebase

Conversation

@benoitcayladbx
Copy link
Copy Markdown
Collaborator

Adding lakebase support for the registry.
Other fixes

Benoit Cayla added 7 commits April 27, 2026 10:37
(a) Add a small psycopg connection pool to LakebaseRegistryStore?
(b) Lazy-load the .lbug graph (skip sync_from_volume on load, fetch on first DT/Build access)?
@benoitcayladbx benoitcayladbx requested a review from a team as a code owner April 29, 2026 12:24
@gitguardian
Copy link
Copy Markdown

gitguardian Bot commented Apr 29, 2026

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
32279171 Triggered Generic Database Assignment a3b55be tests/test_lakebase_auth.py View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

@benoitcayladbx benoitcayladbx merged commit f98f50a into develop Apr 29, 2026
1 check failed
@benoitcayladbx benoitcayladbx deleted the FEAT_RegistryInLakebase branch April 29, 2026 16:12
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