I recently converted a project from using an Account Level API Token to an Organization API Token. Prior to this change the load test script already identifies a ProjectID
in the script options, e.g.,
export let options = {
tags: {
"target": "stage"
},
ext: {
loadimpact: {
projectID: 12345,
name: "project-name"
}
}
}
I see an (400/E5) Authentication error. ProjectID must be specified when using an organization API token when I execute the the load test using CLI version 0.43.1. Example invocation looks like (k6 cloud script_name.js ...args
).
Note: I have already successfully executed k6 login cloud --token VALUE
prior to executing k6 cloud scipt_name.js ...args
).
The most curious behavior of all this (in my opinion) is that when I log into K6 cloud and look at the project details, I see successful K6 run invocations for each of the timestamps where the CLI reported an authentication issue.