-
Notifications
You must be signed in to change notification settings - Fork 39
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
Release/v1.5.0 #115
Release/v1.5.0 #115
Conversation
OP-367: Create release scripts for BE and FE modules
OP-367: removed redundant character from code
remove the edit mode
Add the tools module
OTC-487: Update tblPayment definition in init_test_db.sql
…tribution Add calcrule contribution legacy
OE0-103: Added X_FORWARDED host handle to settings.py
OpenImis official Repo to local develop
updating Readme.md with uninstall when pip package were already deployed on the same environment
OTC-621: Scheduled tasks can be imported from modules directly
* Add support for PG connection settings * Add large script for init_test_db (this required a LOT of tuning, most of the inserts are done in the right order, only the mutual dependencies use the deferred constraints. The mutation will fix those but not yet in this script) * Support for the above in the Python script # Conflicts: # openIMIS/openIMIS/settings.py
PostgreSQL support
add self insuree registration
Django 3.1
Update openimis.json
OP-864 OP-864 CI error from api_fhir_r4 module
Make SQL Server parts optional
release/22.10
|
GitGuardian id | Secret | Commit | Filename | |
---|---|---|---|---|
- | Django Secret Key | 5d71e20 | openIMIS/openIMIS/settings.py | View secret |
- | Django Secret Key | 5d71e20 | openIMIS/openIMIS/settings.py | View secret |
- | Django Secret Key | 9bdc357 | openIMIS/openIMIS/settings.py | View secret |
- | Django Secret Key | 9bdc357 | openIMIS/openIMIS/settings.py | View secret |
🛠 Guidelines to remediate hardcoded secrets
- Understand the implications of revoking this secret by investigating where it is used in your code.
- Replace and store your secrets safely. Learn here the best practices.
- Revoke and rotate these secrets.
- 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
- following these best practices for managing and storing secrets including API keys and other credentials
- install secret detection on pre-commit to catch secret before it leaves your machine and ease remediation.
🦉 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.
Our GitHub checks need improvements? Share your feedbacks!
This pull request introduces 3 alerts when merging fd515c0 into 3126996 - view on LGTM.com new alerts:
Heads-up: LGTM.com's PR analysis will be disabled on the 5th of December, and LGTM.com will be shut down ⏻ completely on the 16th of December 2022. Please enable GitHub code scanning, which uses the same CodeQL engine ⚙️ that powers LGTM.com. For more information, please check out our post on the GitHub blog. |
No description provided.