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

24.08.08 #343

Merged
merged 8 commits into from
Aug 9, 2024
Merged

24.08.08 #343

merged 8 commits into from
Aug 9, 2024

Conversation

Kirans0615 and others added 8 commits July 22, 2024 17:31
Changes to be committed:
	deleted:    docs/bco_scores.json
	modified:   docs/deployment/productionDeployment.md
	new file:   docs/newProductionInstance.md
Changes to be committed:
	modified:   biocompute/apis.py
	modified:   biocompute/urls.py
	modified:   requirements.txt
biocompute-objects/portal_userdb#380

Changes to be committed:
	modified:   .github/workflows/django.yml
	modified:   biocompute/apis.py
	modified:   biocompute/models.py
	modified:   config/settings.py
	modified:   config/urls.py
Updated the function to check locally for the most used schemas. Improves
testing and speed in BCO validation.

Changes to be committed:
	modified:   biocompute/services.py
	renamed:    config/IEEE/2791object.json -> config/schemas/2791object.json
	new file:   config/schemas/dataset_extension.json
	renamed:    config/IEEE/description_domain.json -> config/schemas/description_domain.json
	renamed:    config/IEEE/error_domain.json -> config/schemas/error_domain.json
	renamed:    config/IEEE/execution_domain.json -> config/schemas/execution_domain.json
	new file:   config/schemas/fhir_extension.json
	new file:   config/schemas/galaxy_extension.json
	renamed:    config/IEEE/io_domain.json -> config/schemas/io_domain.json
	new file:   config/schemas/license_extension.json
	renamed:    config/IEEE/parametric_domain.json -> config/schemas/parametric_domain.json
	renamed:    config/IEEE/provenance_domain.json -> config/schemas/provenance_domain.json
	new file:   config/schemas/scm_extension.json
	renamed:    config/IEEE/usability_domain.json -> config/schemas/usability_domain.json
Changes to be committed:
	modified:   biocompute/services.py
	new file:   config/schemas/1.1.0/dataset_extension.json
	new file:   config/schemas/1.1.0/fhir_extension.json
	new file:   config/schemas/1.1.0/galaxy_extension.json
	new file:   config/schemas/1.1.0/license_extension.json
	new file:   config/schemas/1.1.0/scm_extension.json
	renamed:    config/schemas/dataset_extension.json -> config/schemas/1.2.0/dataset_extension.json
	renamed:    config/schemas/fhir_extension.json -> config/schemas/1.2.0/fhir_extension.json
	renamed:    config/schemas/galaxy_extension.json -> config/schemas/1.2.0/galaxy_extension.json
	renamed:    config/schemas/license_extension.json -> config/schemas/1.2.0/license_extension.json
	renamed:    config/schemas/scm_extension.json -> config/schemas/1.2.0/scm_extension.json
	renamed:    config/schemas/2791object.json -> config/schemas/2791/2791object.json
	renamed:    config/schemas/description_domain.json -> config/schemas/2791/description_domain.json
	renamed:    config/schemas/error_domain.json -> config/schemas/2791/error_domain.json
	renamed:    config/schemas/execution_domain.json -> config/schemas/2791/execution_domain.json
	renamed:    config/schemas/io_domain.json -> config/schemas/2791/io_domain.json
	renamed:    config/schemas/parametric_domain.json -> config/schemas/2791/parametric_domain.json
	renamed:    config/schemas/provenance_domain.json -> config/schemas/2791/provenance_domain.json
	renamed:    config/schemas/usability_domain.json -> config/schemas/2791/usability_domain.json
	modified:   config/settings.py
	modified:   requirements.txt
Changes to be committed:
	modified:   Dockerfile
	modified:   docker-compose.yml
	modified:   docs/deployment/dockerDeployment.md
	new file:   entrypoint.sh
Copy link

gitguardian bot commented Aug 9, 2024

⚠️ GitGuardian has uncovered 3 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
4444553 Triggered Company Email Password efebfbe docker-compose.yml View secret
4444553 Triggered Company Email Password efebfbe Dockerfile View secret
11839907 Triggered Django Secret Key 5c5c1f7 config/settings.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.

@HadleyKing HadleyKing merged commit c39a741 into main Aug 9, 2024
4 checks passed
@HadleyKing HadleyKing deleted the 24.08.08 branch August 9, 2024 14:52
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.

2 participants