Summary

Drivers devs currently must create new Silk asset groups for every driver minor release. The steps to do that include fetching credentials from an AWS credentials service and running a series of esoteric shell commands. Many drivers devs do not have access to the Silk web UI, so can't see asset groups or other configurations, making it very difficult to understand what they need to do and if it was successful.

We should create a Github release automation in Drivers Evergreen Tools that teams can use to create the Silk asset groups automatically during minor releases.

Motivation

Who is the affected end user?

Drivers devs and customers who depend on SSDLC data.

How does this affect the end user?

They have to figure out how to create Silk asset groups when doing minor releases. They might accidentally forget to do this step.

How likely is it that this problem or use case will occur?

Every drivers team for every minor release runs into this problem.

If the problem does occur, what are the consequences and how severe are they?

At the least, drivers devs have to take extra time for every minor release. Drivers devs may also not have web access to Silk asset group data, meaning there's not an easy way to know if the proper Silk asset groups were created. If the drivers devs forget to do this step, customers who depend on SSDLC data may have issues upgrading to a new driver version.

Is this issue urgent?

No.

Is this ticket required by a downstream team?

No.

Is this ticket only for tests?

No.

Acceptance Criteria

• Create an automation in Drivers Evergreen Tools that drivers devs can integrate into their Github release workflow that creates Silk asset groups for new driver minor releases.