-
Notifications
You must be signed in to change notification settings - Fork 186
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
GitLab Token issue on ConvertTo-SecureString #87
Comments
Hi Neal, The GitLab and GitHub API's are not quite the same, so this module would not work with it (at least not without some decent amount of modification). As an aside, you can't create a If you really wanted to get a SecureString for some other purpose, you'd get it by doing the following: $cred = Get-Credential
# Enter anything in for username and then enter in your token as the password
$cred.Password # this will be the SecureString
$cred.Password | ConvertFrom-SecureString # this will give you an ASCII representation of the secure string which you can then convert back to a secure string using your previously referenced ConvertTo-SecureString |
Thanks, I'm playing with PSGitLab as well, but can't find a clone/commit function with them. Seems like standard GitHub command line works with GitLab, so I thought maybe the interface was close enough. By the way, I got that "SecureString" code by doing the following: Get-Help Set-GitHubAuthentication -ShowWindow Neal |
Thanks for pointing out the confusing example. That should have been more clear that As for your core concern, cloning and committing should be done directly through git itself. Where a module like this or |
Is this module compatible with GitLab?
I have a token that was working with PSGitLab, but I haven't found a clone feature on that module.
I have modified the token, but it looks roughly like the one below:
$secureString = ('abCdEf1gHIJKL2m_123A' | ConvertTo-SecureString)
Results in this error:
ConvertTo-SecureString : Input string was not in a correct format.
At line:1 char:43
Thanks,
Neal Walters
The text was updated successfully, but these errors were encountered: