opened
deniseyu
username_0
## What challenge are you facing?

In the v5.7 line (possibly earlier) the resource version page will "drop" versions that have been pulled using an outdated resource type image. They still exist in the database and as part of build histories elsewhere, so they're not actually gone, just hiding. I unfortunately did not manage to take a screenshot because Taylor fixed the problem by running `fly check-resource` too quickly 😄 

I'll try to explain using a timeline:

1. Resource `concourse-pr` versions `100`, `101`, `102` fetched with `github-pr` custom resource type version `1.0.0`
1. Authors of `github-pr` publish a new image, versioned `1.0.1`
1. Pipeline automatically pulls that new version, we didn't stick that version because we want the latest and greatest `github-pr` resource type
1. Someone opens a `concourse-pr` and version `104` is fetched using `github-pr` version `1.0.1`
1. On the `concourse-pr` resource history view, I can only see version `104`

This problem goes away if you run `fly check-resource --from version:100`.

## What would make this better?

Defaulting to keeping all resource versions on the page as it was before, if it's possible!

## Are you interested in implementing this yourself?

This involves pretty deep context around how resource configuration versions are computed, so @clarafu would probably need to be involved!
Preserve resource version history when underlying resource type is updated?
issue