CLOUDP-314903 [OIDC] CRD Config Propagation to Automation Config

[MaciejKaras]

Summary

Core Functionality Enhancements:

• Added a new authentication mechanism, MongoDB-OIDC, to the list of supported mechanisms in the authentication_mechanism.go file.
• Introduced the OIDCProviderConfigs field in the AutomationConfig struct and implemented logic to merge and apply OIDC configurations into the deployment in the automation_config.go file.
• Removed default value for groupClaim because the value groups can result in hard to debug misconfiguration.

API and Configuration Updates:

• Added the IsOIDCEnabled() method in the Security struct and AuthResource interface to check if OIDC is enabled.
• Updated the Options struct in the authentication.go file to include OIDCProviderConfigs.

Test Coverage:

• Added comprehensive test cases for OIDC provider configurations in automation_config_test.go, including scenarios for merging, clearing, and modifying configurations.
• Updated the TestAutomationConfigEquality test to include OIDC provider configurations.

JSON Configuration Example:

• Updated the automation_config.json test data file to include sample OIDC provider configurations for testing purposes.

Proof of Work

Checklist

• Have you linked a jira ticket and/or is the ticket in the title?
• Have you checked whether your jira ticket required DOCSP changes?
• Have you checked for release_note changes?

Reminder (Please remove this when merging)

• Please try to Approve or Reject Changes the PR, keep PRs in review as short as possible
• Our Short Guide for PRs: Link
• Remember the following Communication Standards - use comment prefixes for clarity:
  • blocking: Must be addressed before approval.
  • follow-up: Can be addressed in a later PR or ticket.
  • q: Clarifying question.
  • nit: Non-blocking suggestions.
  • note: Side-note, non-actionable. Example: Praise
  • --> no prefix is considered a question

[mircea-cosbuc]

LGTM, I think my comments just require clarification rather than changes.

[lsierant]

I've left few comments: most are minor, but I've put a blocking one regarding MergoDelete.
I also miss a bit a proper e2e test verifying the automation config changes in a real world scenario.

[anandsyncs]

evergreen retry

[lsierant]

LGTM! Great work 👏