Why is it required to provide a s3, azure blob or github blob storage for migrations? (bbs2gh) #1303
-
|
I'm working on a migration where we are already exporting the .tar file from the BitBucket repo via the API. I want to use this repo tar file using Why do I need to provide a storage option? Can the GEI just use the local tar from the machine where the GEI is running without needing to upload to storage? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 9 replies
-
|
The migration happens on the GitHub backend, this CLI is just a wrapper for various API calls. When the backend migration logic runs it needs access to the migration archive, and can’t reach out to your local machine to get it. |
Beta Was this translation helpful? Give feedback.
-
|
thanks for the info, I can repro this and it looks like a bug to me. What I think happened is bbs-server-url used to be optional, and we had the logic that if you provided a server-url you must also provide username/password, but if you didn't provide a server-url then username/password were not required. However, sometime back we realized that in order to process the BBS archive we need the server url (even if you are providing the archive directly via archive-path). However, the arg validation logic wasn't properly updated. You should be able to workaround it by providing any dummy values to get past the validation. And I'll pass this on to the engineering team to file a bug. |
Beta Was this translation helpful? Give feedback.
-
|
Thanks @dylan-smith, passing in dummy creds starts the migration. If I could bug you about one more thing. I'm seeing an error I haven't seen before with the gei, it gets to the ...
..."state":"FAILED","warningsCount":0,"failureReason":"Git source migration failed. Error message: A critical error occurred in the clone step of the git migration.","repositoryName":"ci-image-java-develop"}}}
...
[ERROR] OctoshiftCLI.OctoshiftCliException: Git source migration failed. Error message: A critical error occurred in the clone step of the git migration.Any idea what would cause that clone to fail? I dug into the logs and there's no other message along with that. If this step is trying to clone the repository from GitHub which is being migrated it would make sense that it's failing because the migration isn't complete yet so the repo is in a "Preparing your repository" (or similar) state. This morning I got a little more info on the error saying:
"Clone source" sounds like trying to clone the BBS repository. |
Beta Was this translation helpful? Give feedback.
-
|
@dylan-smith -- ignore the above, this is actually expected behavior on my clients security side. One thing though, why can't we use a bearer authentication type with BBS.. reading through it seems like we can only use username/password. We have a restriction that we need to use Bearer so similarly to |
Beta Was this translation helpful? Give feedback.
-
|
The BBS API to generate a migration archive only supports username/password authentication. Super weird and annoying, but it's something you'd need to take up with Atlassian. |
Beta Was this translation helpful? Give feedback.
-
|
Agh, more hurdles. Thanks again for all the information! |
Beta Was this translation helpful? Give feedback.
The migration happens on the GitHub backend, this CLI is just a wrapper for various API calls. When the backend migration logic runs it needs access to the migration archive, and can’t reach out to your local machine to get it.