Pathogen upload#57
Conversation
Feature/k8
try other outputs in build step
add QMRA models for the admin page
…e collectstatic after the migrations in qmra deployment
add m2m field for QMRAReference in QMRATreatment
remove one2one fields to References in QMRATreatment
…-webapp_explore_yaniv # Please enter a commit message to explain why this merge is necessary, # especially if it merges an updated upstream into a topic branch. # # Lines starting with '#' will be ignored, and an empty message aborts # the commit.
|
| GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
|---|---|---|---|---|---|
| - | - | Generic High Entropy Secret | fa89d51 | infra/terraform/terraform.tfvars | 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 secret safely. Learn here the best practices.
- Revoke and rotate this secret.
- 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.
2 participants
CSV upload and NB fitting to happen in the New Source form (not the inflow section in the main assessment form), with auto-filled min/max fields and a pre-save histogram preview.
That fits the current app structure well because UserSourceForm already owns those 6 concentration inputs and is submitted independently