Uploaded image for project: 'Motor'
  1. Motor
  2. MOTOR-1185

Atlas cluster setup script should create a unique cluster per-invocation, not per commit

XMLWordPrintableJSON

    • Type: Icon: Bug Bug
    • Resolution: Won't Do
    • Priority: Icon: Minor - P4 Minor - P4
    • None
    • Affects Version/s: None
    • Component/s: None
    • None
    • Hide

      DRIVERS-2710:
      setup-atlas-cluster.sh and teardown-atlas-cluster.sh have been updated to ensure that they generate unique atlas clusters per task instead of per commit. both scripts now rely on the default evergreen expansion `task_id`.

      If a driver is calling these scripts while using the `include_expansions_in_env` or `add_expansions_to_env`, no changes should be necessary. If a driver is not providing the `task_id` to the setup and teardown script, the config must be updated to pass this expansion as an environment variable for the scripts.

      Show
      DRIVERS-2710 : setup-atlas-cluster.sh and teardown-atlas-cluster.sh have been updated to ensure that they generate unique atlas clusters per task instead of per commit. both scripts now rely on the default evergreen expansion `task_id`. If a driver is calling these scripts while using the `include_expansions_in_env` or `add_expansions_to_env`, no changes should be necessary. If a driver is not providing the `task_id` to the setup and teardown script, the config must be updated to pass this expansion as an environment variable for the scripts.

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

            Assignee:
            Unassigned Unassigned
            Reporter:
            dbeng-pm-bot PM Bot
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: