Elastic and understanding the spread of versions of `oapi-codegen`

How Elastic were able to easily discover what versions of the oapi-codegen OpenAPI-to-Go code generator was used across the organisation.

Context

At Elastic, there are several versions of the OpenAPI-to-Go code generator, oapi-codegen in use.

Jamie Tanna is a maintainer of oapi-codegen, and as part of joining the company, Jamie wanted to see how Elastic was using different versions of oapi-codegen.

This was also important to know due to ongoing work that Jamie was putting together for the upcoming v2 release of the project, which introduced minimally breaking changes, and would require action from teams to upgrade.

Problem

• What versions of oapi-codegen is in use?
• How many of each version is in use?

Additionally:

• Who are the owners of each service using those versions?

(Note that this exact process has also been used for other internal libraries)

Data

We have the following data in the renovate table:

And the following data in the owners table:

Query

To list the spread of versions, we could write the following query:

select
  package_name,
  version,
  count(*)
from
  renovate
where
  package_name in (
    'github.com/deepmap/oapi-codegen',
    -- due to the way that Go modules work
    'github.com/deepmap/oapi-codegen/v2'
  )
group by
  package_name, version
order by
  version asc

This would produce the following data:

Then, we can also add in ownership information like so:

select
  package_name,
  version,
  count(*),
  group_concat(distinct owner) as owners
from
  renovate
  left join owners on renovate.platform = owners.platform
  and renovate.organisation = owners.organisation
  and renovate.repo = owners.repo
where
  package_name in (
    'github.com/deepmap/oapi-codegen',
    -- due to the way that Go modules work
    'github.com/deepmap/oapi-codegen/v2'
  )
group by
  package_name, version
order by
  version asc

Which would produce the following data: