az functionapp show consistently fails the first time
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 52/100
Research direction
Reproduce the first post-deployment call to the az functionapp function show entry point from the Azure DevOps AzureCLI@2 PowerShell Core step, then compare it with subsequent calls. Done means the command returns a non-null invokeUrlTemplate on its first attempt without requiring an unexplained sleep loop.
Written by the indexing model from the issue text.
Description
As per the title.
Specifically:
Running a yaml pipeline in Azure Devops
modified example below.
- task: AzureCLI@2
displayName: 'Get function urls and keys'
inputs:
azureSubscription: 'xyz'
scriptType: 'pscore'
scriptLocation: 'inlineScript'
inlineScript: |
Write-Host "rgName: $(rgName)"
Write-Host "functionAppName: $(functionAppName)"
$statusUrl = az functionapp function show --resource-group $(rgName) --name $(functionAppName) --function-name 'status' --query 'invokeUrlTemplate'
Write-Host "##vso[task.setvariable variable=statusUrl]$($statusUrl.Trim('"'))"
Specifically any such code like the above always fails the first time after the referenced function is deployed. It seems to work reliably and successfully every other time after.
Do I need to write a sleep loop to address this? :(
Actual Result
ERROR: (NotFound) Error retrieving function.
Code: NotFound
Message: Error retrieving function.
You cannot call a method on a null-valued expression.
At /home/vsts/work/_temp/azureclitaskscript1681431997529_inlinescript.ps1:8 char:57
+ ~~~~~~~~~~~~~~~~~~~~
+ CategoryInfo : InvalidOperation: (:) [], ParentContainsErrorRecordException
+ FullyQualifiedErrorId : InvokeMethodOnNull
##[error]Script failed with exit code: 1
Expected result:
$statusUrl has a non-null value and the script executes as expected.
- Dominant language
- Python
- Stars
- 91
- Forks
- 134
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- No contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/azure-cli-dev-tools
-
Difficulty 1/5 Under an hour Newbie friendliness 65/100
Azure/azure-cli-dev-tools#310 ·
-
ModuleNotFoundError on `azdev extension publish`Possibly taken @german1608 claimed this 370 days ago. Open
Difficulty 4/5 3-5 days Newbie friendliness 38/100
Azure/azure-cli-dev-tools#529 ·
-
Check random default into metadata change whitelist.txtMay be free again @AllyW claimed this 524 days ago, and no pull request is open. Open
Azure/azure-cli-dev-tools#525 · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Azure/azure-cli-dev-tools#520 ·
-
`azdev extension remove` does not clear its corresponding source code path in `sys.path` when its package name is not its folder nameMay be free again @AllyW claimed this 561 days ago, and no pull request is open. Open
Azure/azure-cli-dev-tools#519 · 1 comment · 1 reaction · 1 assignee ·
All issues in Azure/azure-cli-dev-tools
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
huggingface/peft#3955 ·
Maintainers usually reply within 1 day
-
author-page correction
Difficulty 2/5 1-3 hours Newbie friendliness 60/100
acl-org/acl-anthology#10313 ·
Maintainers usually reply within 1 day
-
anime duplicate exception request-theme
Difficulty 1/5 Under an hour Newbie friendliness 82/100
LizardByte/ThemerrDB#8926 · 1 comment ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
huggingface/transformers#49556 ·
Maintainers usually reply within 1 day
-
area/security bug
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
mozilla-ai/otari#2245 ·
Maintainers usually reply within 1 day