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

auth default null values #2608

Merged
merged 3 commits into from
Oct 13, 2023
Merged

auth default null values #2608

merged 3 commits into from
Oct 13, 2023

Conversation

jessegoodier
Copy link
Collaborator

What does this PR change?

remove default saml and OIDC values, which should be null.

Does this PR rely on any other PRs?

How does this PR impact users? (This is the kind of thing that goes in release notes!)

Links to Issues or tickets this PR addresses or fixes

What risks are associated with merging this PR? What is required to fully test this PR?

How was this PR tested?

Have you made an update to documentation? If so, please provide the corresponding PR.

@chipzoller
Copy link
Collaborator

I'd leave the chart version bump for another PR so we have nicer organization.

@AjayTripathy
Copy link
Contributor

yeah lgtm just dont change chart version in prs that arent release related?

@jessegoodier jessegoodier marked this pull request as ready for review October 13, 2023 17:37
@gitguardian
Copy link

gitguardian bot commented Oct 13, 2023

⚠️ GitGuardian has uncovered 1 secret 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 secret in your pull request
GitGuardian id Secret Commit Filename
7414 Google API Key 365c2a7 cost-analyzer/templates/aggregator-statefulset.yaml 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 secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  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!

@jessegoodier jessegoodier merged commit 7b02ed0 into develop Oct 13, 2023
8 checks passed
@jessegoodier jessegoodier deleted the saml-values-update branch October 13, 2023 18:04
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

3 participants