This request has not been added to the review queue. It should be placed in the appropriate store-requests subcategory using the subcategory template for classic-confinement, privileged-interfaces and aliases requests.
Hello, any news regarding this topic?
This request has been added to the queue for review by the @reviewers team.
Hello @AndreiDodu!
Considering that a user can easily clone a repository to a local directory and copy the files to an external device, I’m not sure this is a reasonable request. What do other @reviewers think?
Hi @yomonokio , I just want to clarify that FromGtoG is a bulk migration tool. It clones all the repositories a user might have. I don’t know how many people might have GBs and GBs of repositories on Github/Gitea or Gitlab. Ideally, most people have just a few repositories. But if we’re talking about an organization, I imagine they have more.
Thank you,
Andrei
Hello, and thank you for the additional info!
Auto-connection is not typically granted for removable-media as defined in the process for auto-connections. Given it is a small subset of users that would benefit from the auto-connection, this is a -1 (#voteAgainst) from me.
Does manual-connection suffice for the users, like organizations, that would desire this functionality?
yes, it’s enough. Thank you @elisehdy
I agree with @elisehdy and manual connection would be a better fit in this case. +1 from me for granting FromGtoG manual connection to the removable media interface (#voteFor). Just realized that removable can always be manually connected without any special snap-declaration.
Similar to Noc-convert: auto-connection request for removable-media - #9 by jslarraz, the usual guidance in this case is to use snapctl is-connected to detect if the removable-media interface is already connected and prompt the user to manually connect it when needed
Thank you @jslarraz for your response.
