Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Old pseudo-versioned plans need to be migrated to new system #108

Open
calebissharp opened this issue Dec 19, 2019 · 2 comments
Open

Old pseudo-versioned plans need to be migrated to new system #108

calebissharp opened this issue Dec 19, 2019 · 2 comments

Comments

@calebissharp
Copy link
Contributor

The previous "versioning" that was done created multiple plans for an agreement. These records should be updated to all have the same canonical_id value (most likely set to the id of the latest plan), and related plan_version rows created. Preferably, this will be some kind of script that we will run once after merging the versioning changes into prod.
This was referenced Jan 15, 2020
Closed
Closed
@LisaMoore1
Copy link
Collaborator

@calebissharp RAN099952 amendments were all created after versioning work so not sure if using the amend workflow created pseudo versions or actual versions (using new versioning system)

@calebissharp
Copy link
Contributor Author

@LisaMoore1 That would be the old way still. bcgov/range-web#475 implements the new versioning for amendments.

@calebissharp calebissharp mentioned this issue Mar 12, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@calebissharp @LisaMoore1