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

Issue using BoxStarter test runner module with Artifactory API keys #472

Open
kirannhegde opened this issue Jul 15, 2021 · 1 comment
Open
Labels
0 - _Triaging Issue is accepted, but a milestone has yet to be added for the issue Bug Issues where something has happened which was not expected or intended

Comments

@kirannhegde
Copy link

What You Are Seeing?

I am trying to use the Boxstarter test runner's PowerShell cmdlet: Set-BoxstarterDeployOptions. As arguments to this cmdlet, i am providing the URL to our internal Artifactory server using the DefaultNugetFeed parameter. I am trying to use the API key using the parameter : DefaultFeedAPIKey. However, I am running into the following issue:

Cannot process argument transformation on parameter 'DefaultFeedAPIKey'. Cannot convert
value "**<my API key>**" to type "System.Guid". Error: "Guid
should contain 32 digits with 4 dashes (xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx)."
At line:1 char:295

    ... tFeedAPIKey AKCp8hzDDZBqPt1TBD3uRVdfTw8NpwR9A5iySWZHdtdykFyrUgfpZDHNC ...
    ~~~~~~~~~~~~~
        CategoryInfo : InvalidData: (:) [Set-BoxstarterDeployOptions], ParameterBindingArgumentTransformationEx
        ception
        FullyQualifiedErrorId : ParameterArgumentTransformationError,Set-BoxstarterDeployOptions

What Is Expected?

The cmdlet should be able to process API keys which are in excess of 32 characters in length.

How Did You Get This To Happen? (Steps to Reproduce)

Execute Set-BoxstarterDeployOptions with an API key that is in excess of 32 characters in length.

@kirannhegde kirannhegde added the Bug Issues where something has happened which was not expected or intended label Jul 15, 2021
@pauby pauby added 0 - _Triaging Issue is accepted, but a milestone has yet to be added for the issue Up For Grabs labels Jul 15, 2021
@pauby
Copy link
Member

pauby commented Jul 15, 2021

Based on the comment for the issue I closed today we may not be able to provide as much support on the Testrunner modules so I have put this Up For Grabs'. PR's welcome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
0 - _Triaging Issue is accepted, but a milestone has yet to be added for the issue Bug Issues where something has happened which was not expected or intended
Projects
None yet
Development

No branches or pull requests

2 participants