ERROR: Unable to retrieve url https://raw.githubusercontent.com/........
Closed this issue · 12 comments
Hi all,
I'm getting the below error message from within my Azure pipeline.
ERROR: Unable to retrieve url https://raw.githubusercontent.com/thuas-itops/azure-monitor-baseline-alerts-tst/main/patterns/alz/alzArm.json
In my github repo I see the following.
Any idea what is going wrong?
Hello @jerrolmossel ,
thanks for your feedback. Are you able to see the file from the <> Code menu?
Thanks,
Bruno.
strange that you see mine in your fork ... click on the Raw button and copy the URL from the browser address bar ... what does it look like?
https://[raw.githubusercontent.com/thuas-itops/azure-monitor-baseline-alerts-tst/main/patterns/alz/alzArm.json?token=GHSAT0AAAAAACPUDD5SIZYVDXWTCB5W5TJAZPUO3FA]
Should it be a forked repo? The documentation says so but I've cloned it to make it a private repo.
it's ok, just take the first part without the token and make sure it looks formatted like this
https://raw.githubusercontent.com/thuas-itops/azure-monitor-baseline-alerts-tst/main/patterns/alz/alzArm.json
Ok, but that's the same path I have in my sample-pipeline.yml
variables:
location: "westeurope"
ManagementGroupPrefix: "hhs"
serviceConnectionName: "AMBA-Service-Connection"
pool:
vmImage: ubuntu-latest
steps:
- task: AzureCLI@2
displayName: "Deploy AMBA ARM template"
inputs:
azureSubscription: ${{ variables['serviceConnectionName'] }}
scriptType: bash
scriptLocation: inlineScript
inlineScript: |
az deployment mg create --template-uri https://raw.githubusercontent.com/thuas-itops/azure-monitor-baseline-alerts-tst/main/patterns/alz/alzArm.json --location$(location) --management-group-id $ (ManagementGroupPrefix) --parameters ./patterns/alz/alzArm.param.json
did you make your repo public or managed the access correctly?
did you make your repo public or managed the access correctly?
What is a best practice?
I'm seeing a lot of forked repo's by other github members but I rarely see customer data in the alzArm.param.json or sample-pipeline.yml of those forked repo's.
The best practice and the documented way is to fork. Please fork it and let me know.
@Brunoga-MS
I changed the repo from private to public and I could run my azure pipeline succesfully so it has to be an access/authorization problem at my side.
Thank you for thinking along. Issue solved. I will follow up your advice to fork according the documentation :) .
@jerrolmossel ,
glad that the issue got resolved. Based on that I am going to close it as resolved.
Thanks,
Bruno