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.

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

Open
wants to merge 107 commits into
base: develop
Choose a base branch
from

Conversation

anzioka
Copy link
Contributor

@anzioka anzioka commented Feb 16, 2022

No description provided.

@anzioka anzioka requested review from njhlai and and-carter February 16, 2022 18:17
Copy link
Contributor

@geekbeast geekbeast left a 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.

Comment on lines 181 to 186
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()
Copy link
Contributor

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.

@anzioka
Copy link
Contributor Author

anzioka commented Feb 16, 2022

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.

Yes, this writes to existing table in chronicle db

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants