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

rebase #78

Closed
wants to merge 63 commits into from
Closed

rebase #78

wants to merge 63 commits into from

Conversation

Myron-Woods-IBM
Copy link
Contributor

No description provided.

faraz and others added 30 commits November 14, 2023 23:48
…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
Adding a CNAME file to the static directory to prevent our custom URL…
NGINX 413 Payload Too Large Documentation
Temporarily disabling CNAME in static directory
Signed-off-by: faraz <afaraz@protonmail.com>
Signed-off-by: faraz <afaraz@protonmail.com>
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
awang129 and others added 28 commits November 27, 2023 11:24
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>
Signed-off-by: gtiwari-ibm <144962723+gtiwari-ibm@users.noreply.github.com>
created and organized graphql page, filled out lambda functions section, cleaned up and clarified workflows page
IER and Disposition Updates
Dispostion part Updated
Signed-off-by: kramerro-ibm <102995992+kramerro-ibm@users.noreply.github.com>
several additions and updates (css, organization, cleanup)
Copy link

gitguardian bot commented Nov 28, 2023

⚠️ 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 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
  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.

6 participants