-
Notifications
You must be signed in to change notification settings - Fork 3
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
rebase #78
rebase #78
Conversation
… the actions we perform in the doc
…e storage classes we created in AWS
redacted slack bot token secret
…be a part of the build, and I updated the ier_config settings and fixed the formatting
Fixing a broken link in the operator.mdx
… from being overwritten
Adding a CNAME file to the static directory to prevent our custom URL…
NGINX 413 Payload Too Large Documentation
Adding IER jar fix
Temporarily disabling CNAME in static directory
Signed-off-by: faraz <afaraz@protonmail.com>
Signed-off-by: faraz <afaraz@protonmail.com>
Update docusaurus.config.js
Don't need this. Signed-off-by: Angela Wang <125045410+awang129@users.noreply.github.com>
Don't need this Signed-off-by: Angela Wang <125045410+awang129@users.noreply.github.com>
Configure IER on ICN
ICN and IER Configuration
Signed-off-by: Angela Wang <125045410+awang129@users.noreply.github.com>
Signed-off-by: Angela Wang <125045410+awang129@users.noreply.github.com>
Signed-off-by: Angela Wang <125045410+awang129@users.noreply.github.com>
Signed-off-by: Angela Wang <125045410+awang129@users.noreply.github.com>
Signed-off-by: Angela Wang <125045410+awang129@users.noreply.github.com>
Angela updates
Signed-off-by: gtiwari-ibm <144962723+gtiwari-ibm@users.noreply.github.com>
…ating IER object stores
created and organized graphql page, filled out lambda functions section, cleaned up and clarified workflows page
IER and Disposition Updates
Dispostion part Updated
Update ier.mdx
Fixed Align.md
Signed-off-by: kramerro-ibm <102995992+kramerro-ibm@users.noreply.github.com>
…s, added web pd to lessons learned
Merging in of latest changes
… case, some cleanup
several additions and updates (css, organization, cleanup)
|
GitGuardian id | Secret | Commit | Filename | |
---|---|---|---|---|
8782363 | Slack Bot Token | ef292da | docs/3-Create/use-cases/event_actions.mdx | View secret |
8782363 | Slack Bot Token | 424fb72 | docs/3-Create/use-cases/event_actions.mdx | View secret |
8782363 | Slack Bot Token | 40c1343 | docs/3-Create/use-cases/async_replication.mdx | 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.
Our GitHub checks need improvements? Share your feedbacks!
No description provided.