Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature/api #668

Merged
merged 55 commits into from
Jun 26, 2024
Merged

Feature/api #668

merged 55 commits into from
Jun 26, 2024

Conversation

andre-merzky
Copy link
Member

add future api draft (not user visible)

@andre-merzky andre-merzky self-assigned this Jun 26, 2024
@andre-merzky andre-merzky merged commit d1aecc7 into devel Jun 26, 2024
1 of 3 checks passed
@andre-merzky andre-merzky deleted the feature/api branch June 26, 2024 11:51
Copy link

gitguardian bot commented Jun 26, 2024

⚠️ GitGuardian has uncovered 7 secrets 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 secrets in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
4806626 Triggered MongoDB Credentials 613bc6f examples/misc/lfs_tagging_dd.py View secret
4806628 Triggered MongoDB Credentials f4f7ef7 .travis.yml View secret
4806629 Triggered MongoDB Credentials 2b18268 tests/test_integration/tagging_lfs_rp_da_scheduler.py View secret
4806629 Triggered MongoDB Credentials f4f7ef7 tests/test_component/test_tproc_rp_2.py View secret
4806634 Triggered MongoDB Credentials f4f7ef7 tests/jenkins_run.sh View secret
4806635 Triggered MongoDB Credentials f4f7ef7 examples/user_guide/add_shared_data.py View secret
12232033 Triggered Generic Database Assignment f4f7ef7 tests/test_component/test_amgr.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 secrets safely. Learn here the best practices.
  3. Revoke and rotate these secrets.
  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.

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

Successfully merging this pull request may close these issues.

1 participant