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

BUG: bbs2gh migrate-repo --no-ssl-verify can only be provided with BBS Server URL While Providing the URL #1317

Open
ryaugusta opened this issue Dec 18, 2024 · 1 comment · May be fixed by #1318
Labels
bug Something isn't working

Comments

@ryaugusta
Copy link

Description

I need to pass the --no-ssl-verify command when running the migrate-repo command but am seeing the error:
[ERROR] --no-ssl-verify can only be provided with --bbs-server-url.

I am passing the --bbs-server-url but this exception is still being caught for some reason;

My command:

gh bbs2gh migrate-repo \
  --archive-path <path-to-tar-file>.tar \
  --github-org GITHUB_ORG \
  --github-repo NEW_GITHUB_REPO \
  --bbs-server-url BBS_SERVER_URL \
  --bbs-project BBS_PROJECT \
  --bbs-repo BBS_REPO \
  --no-ssl-verify \
  --use-github-storage

I am providing the --bbs-server-url, which is the requirement to being able to use the --no-ssl-verify command.

Is there a way to install an older version of the bbs2gh extension so see if this bug arose from v1.11.0

Reproduction Steps

Run the gh bbs2gh migrate-repo command and supply a bbs-server URL as well as --no-ssl-verify

@ryaugusta ryaugusta added the bug Something isn't working label Dec 18, 2024
@dylan-smith
Copy link
Collaborator

dylan-smith commented Dec 18, 2024

I think this error is correct. You are passing --archive-path meaning the migration will use the archive file you provide instead of calling BBS API's. Since it is not going to be calling BBS API's the --no-ssl-verify option is not applicable.

The error message could be updated to be more accurate/helpful though.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants