Either will do for add-credential. It's just that you won't be able to bootstrap when building from source on OS X. (You can, but it's not straightforward, and isn't needed to test this bug fix anyway.)
> When I tried building off of the master branch on OSX, I encountered the async app object issue you mentioned, and it sounds like that won't be resolved, unless I build from source and test on Linux. Is that accurate?
Just to be clear, there's a new PR that has landed since comment #17, that should fix the async issue. i.e. it should resolve the issue that lead to the error message
ERROR finalizing credential: ad.ServicePrincipalsClient#Create: Failure
responding to request: StatusCode=0 -- Original Error: autorest/azure:
Service returned an error. Status=404 Code="Request_ResourceNotFound"
Message=""
> Did you want me to test and build off of the master branch?
Off the "develop" branch please.
> Do you want me to test via SP or the interactive CLI?
Interactive CLI (i.e. juju add-credential, select "interactive")
> Did you want me to test on OSX or Linux?
Either will do for add-credential. It's just that you won't be able to bootstrap when building from source on OS X. (You can, but it's not straightforward, and isn't needed to test this bug fix anyway.)
> When I tried building off of the master branch on OSX, I encountered the async app object issue you mentioned, and it sounds like that won't be resolved, unless I build from source and test on Linux. Is that accurate?
Just to be clear, there's a new PR that has landed since comment #17, that should fix the async issue. i.e. it should resolve the issue that lead to the error message
ERROR finalizing credential: ad.ServicePrinc ipalsClient# Create: Failure ResourceNotFoun d"
responding to request: StatusCode=0 -- Original Error: autorest/azure:
Service returned an error. Status=404 Code="Request_
Message=""
As above, the OS shouldn't matter.
Thanks in advance!