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/move mapa to new stack #150

Open
wants to merge 12 commits into
base: main
Choose a base branch
from
Open

Conversation

dieh
Copy link
Contributor

@dieh dieh commented Aug 3, 2022

No description provided.

@lpirola
Copy link
Contributor

lpirola commented Sep 1, 2022

@dieh tem conflito pra resolver antes de fazer merge. Ainda quer fazer, certo?

@dieh
Copy link
Contributor Author

dieh commented Sep 5, 2022

@dieh tem conflito pra resolver antes de fazer merge. Ainda quer fazer, certo?

sim, quero sim. resolvi os conflito, agora :)

@gitguardian
Copy link

gitguardian bot commented Apr 10, 2023

⚠️ GitGuardian has uncovered 10 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
- Generic Password 842faed mapa/docker-compose.yml View secret
- Generic Password 1d045bf mapa/docker-compose.yml View secret
- Generic Password c0ec874 listeners/docker-compose.yml View secret
- Generic Password 842faed mapa/docker-compose.yml View secret
- Generic Password 3b69625 mapa/docker-compose.yml View secret
- Generic Password 842faed mapa/docker-compose.yml View secret
- Generic Password 3b69625 mapa/docker-compose.yml View secret
- Generic Password c0ec874 listeners/docker-compose.yml View secret
- Generic Password 1d045bf mapa-2/docker-compose.yml View secret
- Generic Password 48ee1af events-scheduled/docker-compose.yml 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!

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