-
Notifications
You must be signed in to change notification settings - Fork 0
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
🎈 Elasticsearch #34
🎈 Elasticsearch #34
Conversation
|
GitGuardian id | GitGuardian status | Secret | Commit | Filename | |
---|---|---|---|---|---|
9607557 | Triggered | Generic High Entropy Secret | ef8bc8c | app/classes/search-ui.jsx | View secret |
9607557 | Triggered | Generic High Entropy Secret | 124c747 | search/search-ui.jsx | View secret |
9607557 | Triggered | Generic High Entropy Secret | e7875df | app/data/searchkit.json | View secret |
9607557 | Triggered | Generic High Entropy Secret | e7875df | app/classes/search-ui.tsx | View secret |
9607557 | Triggered | Generic High Entropy Secret | cb4ebd7 | app/classes/search-ui.tsx | View secret |
9607557 | Triggered | Generic High Entropy Secret | cb4ebd7 | app/classes/search-ui.jsx | 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.
* vite: CLI helper Working production build!!! Adds publicDir to fix build error Empty outDir on build Fixes docker build steps Updates package versions Fixes build error Updates npm run scripts Removes old jsconfig file Fixes CSS stylesheet inclusion Migrate to Vite
* main: (33 commits) Working Organ catalog resolver!!! Initial catalog resolver logic Fixes AAPBRecords without a time component Combines get exhibit / collections logic to Fixes Exhibit fetch error logic Link to pages by slug 'remove fetch2 code because error boundary handles error bubbling' 'remove fetch2' 'a little bit of margin in my rooooot' 'last fix for sidebar positioning, look up pages by slug, backarrow icon on hover on footnote' 'extra space' 'fix sidebar stacking' 'photo updates' 'style footnote element, correct footnote numbers' 'working crazy footnotes' 'wip footnotes' 'author sidebar section, fix exhibit height in portrait' Working URL resolver! Possible structure for old OV /exhibits/ Updates dependencies ...
* main: Fixes carousel clicks by unsetting z-index Make legend visible on small screens Uses fixed height for carousel Upgrades dependencies Fixes carousel height issues
Elasticsearch
Basic elasticssearch component. Includes
content_type
facetsfeatured
filterCloses WGBH-MLA/ov-wag#122
Done
Todo
Search Requests from June 28 Demo
Optional