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

Production Release June Week 4 #883

Merged
merged 22 commits into from
Jun 27, 2022
Merged

Production Release June Week 4 #883

merged 22 commits into from
Jun 27, 2022

Conversation

gigincg
Copy link
Member

@gigincg gigincg commented Jun 24, 2022

No description provided.

ishanExtreme and others added 18 commits June 14, 2022 01:52
* assets permission class added

* permissions added to assetlocation model

* DRY permission added to assetlocation viewset

* Assets Permission updated

Co-authored-by: Extreme <extreme@pop-os.localdomain>
* docs (CONTRIBUTING): fixed docker compose command

* Use native docker compose

Co-authored-by: Vignesh Hari <vichuhari100@gmail.com>
* update sentry sdk

* fix precommit

* make sentry more configurable

added SENTRY_ENVIRONMENT to set environment
and SENTRY_TRACES_SAMPLE_RATE to set trace sample rate

* merge common deployment config

* add redis integration for sentry

* ignore django.security.DisallowedHost events

Co-authored-by: Shivank Kacker <kacker.shivank@gmail.com>
* Make the meta field optional in asset

* Make the meta field optional in bed tables

* Remove default in optional meta fields

* Update migrations

* Remove null and keep defaults

* Update migrations

* Fix migrations
Changed default VAPID keypair
fixed plural for local body in admin
notes endpoint made role responsive

Co-authored-by: Extreme <extreme@pop-os.localdomain>
@gigincg gigincg requested a review from a team as a code owner June 24, 2022 04:58
@gitguardian
Copy link

gitguardian bot commented Jun 24, 2022

⚠️ GitGuardian has uncovered 2 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 Secret Commit Filename
196640 Generic Private Key 724a974 config/settings/base.py View secret
196640 Generic Private Key 84af660 config/settings/base.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.

Our GitHub checks need improvements? Share your feedbacks!

@vigneshhari vigneshhari temporarily deployed to Staging-egov June 24, 2022 13:02 Inactive
aeswibon and others added 2 commits June 26, 2022 21:40
Fixed created_by field value
Co-authored-by: Extreme <extreme@pop-os.localdomain>
@vigneshhari vigneshhari temporarily deployed to Staging-egov June 26, 2022 16:21 Inactive
@mathew-alex mathew-alex merged commit c889447 into production Jun 27, 2022
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.

None yet