-
Notifications
You must be signed in to change notification settings - Fork 93
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
Lab 2 - Task 3 - step 10 Powershell fails #7
Comments
There are setup instructions at https://github.com/solliancenet/ai-in-a-day/blob/main/setup/03-setup-workspace.md on which resources need to be created for the lab. It does look like the instructions could be clearer about needing to go through this setup process first assuming you are running this in your own home lab rather than someplace which has incorporated the setup instructions into a deployment process.
I'm not sure what steps you used to do this, but you shouldn't need to connect to an Azure account. You should be able to copy the code exactly as it appears in the code block, paste it into a PowerShell prompt by right-clicking, strike Enter, and create the function. If you are getting an error, can you show a screenshot of what you're doing and the error?
This is a custom function to do a specific task, so there won't be other examples of it. |
|
Run pwsh.exe on whatever machine you downloaded the files to in step 8. If that's the lab VM, then yes, you would open PowerShell on the lab VM; if you downloaded the six files to a local machine, then open PowerShell on the local machine. The task is invoking web requests against your Azure Search service which has already been created. In step 11, you pass in the account name and API key as parameters (for ease of use; alternatively, they could come from environment variables or secure storage). That's why there's no requirement to use Azure PowerShell modules. |
Thank you for your quick reply. |
I see there has been 'toggling' with the Lab numbers and titles. To be clear;
This step 10 is not clear.
The text was updated successfully, but these errors were encountered: