Use AWS Secrets Manager for Evergreen Test Secrets

XMLWordPrintableJSON

    • Type: Epic
    • Resolution: Unresolved
    • Priority: Unknown
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Use AWS Secrets Manager for AWS-Related Test Secrets
    • Ruby Drivers
    • None
    • Hide
      1. What would you like to communicate to the user about this feature?
      2. Would you like the user to see examples of the syntax and/or executable code and its output?
      3. Which versions of the driver/connector does this apply to?
      Show
      1. What would you like to communicate to the user about this feature? 2. Would you like the user to see examples of the syntax and/or executable code and its output? 3. Which versions of the driver/connector does this apply to?
    • In Progress
    • 2
    • 1
    • 3
    • 100
    • 50
    • 🟡 Potential Risk
    • Hide

      After initial investigation it became clear that the existing Ruby driver test infrastructure does not get along well with the secrets manager. The team decided to streamline our testing infrastructure in scope of this ticket. This require some additional time (hence the confidence status), but this needs to be done finally.

      As of September 26th, the infrastructure is migrated, and circa 60% of tests configurations are green; this week we can actually start working on secrets manager for complex setups.

      Show
      After initial investigation it became clear that the existing Ruby driver test infrastructure does not get along well with the secrets manager. The team decided to streamline our testing infrastructure in scope of this ticket. This require some additional time (hence the confidence status), but this needs to be done finally. As of September 26th, the infrastructure is migrated, and circa 60% of tests configurations are green; this week we can actually start working on secrets manager for complex setups.
    • Hide

      2025-10-14 - 🟡 Potential Risk
      There was not much progress on the ticket since Dmitry was sick one week. FLE test runner needs to be updated to streamline with drivers evergreen tools, as well as all aws tests. Basically, moving to the new tools take more time, than actually introducing the secrets manager.

      2025-09-30 - 🟡 Potential Risk
      After initial investigation it became clear that the existing Ruby driver test infrastructure does not get along well with the secrets manager. The team decided to streamline our testing infrastructure in scope of this ticket. This require some additional time (hence the confidence status), but this needs to be done finally.

      As of September 26th, the infrastructure is migrated, and circa 60% of tests configurations are green; this week we can actually start working on secrets manager for complex setups.


      Show
      2025-10-14 - 🟡 Potential Risk There was not much progress on the ticket since Dmitry was sick one week. FLE test runner needs to be updated to streamline with drivers evergreen tools, as well as all aws tests. Basically, moving to the new tools take more time, than actually introducing the secrets manager. 2025-09-30 - 🟡 Potential Risk After initial investigation it became clear that the existing Ruby driver test infrastructure does not get along well with the secrets manager. The team decided to streamline our testing infrastructure in scope of this ticket. This require some additional time (hence the confidence status), but this needs to be done finally. As of September 26th, the infrastructure is migrated, and circa 60% of tests configurations are green; this week we can actually start working on secrets manager for complex setups.
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      This ticket was split from DRIVERS-2585, please see that ticket for a detailed description.

            Assignee:
            Dmitry Rybakov
            Reporter:
            TPM Jira Automations Bot
            None
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

              Created:
              Updated:
              None
              None
              None
              None
              None

                Estimated:
                Original Estimate - 2 weeks
                2w
                Remaining:
                Remaining Estimate - 2 weeks
                2w
                Logged:
                Time Spent - Not Specified
                Not Specified