-
Notifications
You must be signed in to change notification settings - Fork 1
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.
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
migrate app usage survey data to v3 #162
base: develop
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This requires an existing table to export locally on the chronicle db box, correct?
This is also only an export job not an import job correct? It seems like we could just pg_dump this table to new stack, but just want to confirm this isn't expected write directly into new stack.
val adminRoleAclKey = organizations[orgId]?.adminRoleAclKey | ||
if (adminRoleAclKey == null) { | ||
logger.warn("skipping {} since it doesn't have admin role", orgId) | ||
return@org | ||
} | ||
val adminPrincipals = principalService.getAllUsersWithPrincipal(adminRoleAclKey).map { it.principal }.toSet() |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think you might need the super user here, this is one of the issues we faced while doing study + participant migration.
Yes, this writes to existing table in chronicle db |
…4-migrate-app-usage-survey
…to task/LATTICE-3024-migrate-app-usage-survey
…LATTICE-3024-migrate-app-usage-survey
…-migrate-app-usage-survey
…migrate-app-usage-survey
No description provided.