-
Notifications
You must be signed in to change notification settings - Fork 90
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
Groups migration fails if a local group is not found on the account level, when we explicitly select that group in config #312
Comments
At the moment, it's the expected behavior. Run with auto:true with groups config |
It would be better if the tool just log the issue without failing. |
@mwojtyczka we could also do that but will it not leave the migration in the incomplete state? |
Why? the groups anyway only exists in the workspace. There is nothing we can do if they are not in the account. Does that issue also exist if we run it the tool for all groups (not only selected)? |
to properly support this, we have to be able to re-run the group migration step |
Agree with @nfx - this should be idempotently runnable. |
@nfx what's the verdict? |
I run the tool with selected group. One of the group did not exist in the account. The tool failed and stopped.
Enclosed stacktrace and standard output.
stacktrace.txt
The text was updated successfully, but these errors were encountered: