Skip to content
This repository was archived by the owner on Sep 30, 2024. It is now read-only.

oobmigration: Add additional behavior around versions#39474

Merged
efritz merged 7 commits into
mainfrom
ef/oobmigration-versions
Jul 27, 2022
Merged

oobmigration: Add additional behavior around versions#39474
efritz merged 7 commits into
mainfrom
ef/oobmigration-versions

Conversation

@efritz

@efritz efritz commented Jul 27, 2022

Copy link
Copy Markdown
Contributor

This PR adds a new functions to the oobmigration package to help with version operations.

Test plan

New unit tests.

}

func (v Version) GitTag() string {
return fmt.Sprintf("v%d.%d.0", v.Major, v.Minor)

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

patch doesn't matter?

Copy link
Copy Markdown
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

No, we only track major/minor in oobmigration tables, so you can't actually introduce one in a patch (I think that's explicitly documented but I should double-check).

Also the way we're handing upgrades will be some version -> minor version, zero patch, and then you can do the regular update flow to your patch version if you want to (literally just migrate to X.Y.0, then launch X.Y.Z and the migrator will do the small, if any, schema upgrade).

Comment thread internal/oobmigration/version.go Outdated
@efritz efritz enabled auto-merge (squash) July 27, 2022 13:35
@efritz efritz merged commit e99a573 into main Jul 27, 2022
@efritz efritz deleted the ef/oobmigration-versions branch July 27, 2022 13:43
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants