Skip to content
This repository was archived by the owner on Apr 13, 2020. It is now read-only.

Conversation

@dennisseah
Copy link
Collaborator

closes: microsoft/bedrock#1281

this is what we get when PAT is incorrect

code: 1000
message: setup-cmd-failed: Setup command was not successfully executed.
  code: 1400
  message: setup-cmd-core-api-err: Could not get Core API client. Check the Azure credential.
  details: Failed request: (401)

"setup-cmd-prompt-err-no-subscriptions": "No subscriptions found.",
"setup-cmd-prompt-err-subscription-missing": "Subscription Identifier was missing.",
"setup-cmd-prompt-err-input-file-missing": "{0} did not exist or not accessible. Make sure that it is accessible.",
"setup-cmd-core-api-err": "Could not get Core API client. Check the Azure credential",
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Core API is also for Azure DevOps. Let's be specific so we don't confuse the user between Azure and Azure DevOps here.

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you suggest a good message? thanks

Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The same message as the other errors:

Something like
Could not initialize Core API client. Check the Azure DevOps credentials.

This is just being explicit about Azure vs Azure DevOps

Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

actually, this one is for Azure and not Azure DevOps. the other 2 are for Azure DevOps. We are using PAT to authenticate for this one and using Service Principal for the other 2.

@dennisseah dennisseah requested a review from andrebriggs April 6, 2020 23:18
@dennisseah
Copy link
Collaborator Author

integration test results

fabrikam-hld-to-fabrikam-manifests has pipeline id of 423
Get the build status for build...
pipeline: fabrikam-hld-to-fabrikam-manifests-423:
pipeline_status this iteration --> "completed"
Successful build for pipeline: fabrikam-hld-to-fabrikam-manifests-423!
info:    Generating config.yaml from yaml file input.
info:    config.yaml was generated and located at /Users/veseah/.spk/config.yaml.
info:    Successfully initialized the spk tool!
Start Time           Service      Deployment   Commit  Src to ACR Image Tag                                             Result ACR to HLD Env    Hld Commit Result HLD to Manifest Result
4/6/2020, 8:17:28 PM fabrikam2019 51fb5e6d1b4f 52eebd5 711        fabrikam2019-fabrikam.acme.frontend:master-20200407.1 ✓      711        MASTER 4d88c1f    ✓      712             ✓     
1 deployment(s) were returned by spk deployment get
Verified that srcPipeline:711 acrPipelineId:711 hldPipelineId:712 pullrequest:"368" are all linked together correctly.
Successfully reached the end of spk deployment get tests.

@dennisseah dennisseah merged commit 6b653ee into master Apr 7, 2020
@dennisseah dennisseah deleted the issue1281 branch April 7, 2020 03:38
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

CLI setup command give 401 error with incorrect PAT

5 participants