Deployment action is selecting the wrong subscription
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- azure, github-actions, javascript
Research direction
Reproduce the workflow using an Azure container registry in GLOBAL-SUBSCRIPTION and a Function container app in DEMO-SUBCRIPTION. Start with the Azure/functions-container-action@v1 inputs and the debug request to /subscriptions/; trace how the subscription is selected. Done means the action targets the app subscription while using the separate registry, or clearly documents that co-location is required.
Written by the indexing model from the issue text.
Description
I have the following set up in Azure
-
A 'global' subscription i.e.
GLOBAL-SUBSCRIPTION- My Azure container registry belongs to the
GLOBAL-SUBSCRIPTION
- My Azure container registry belongs to the
-
A 'per-environment' subscription e.g. a 'demo' subscription
DEMO-SUBCRIPTION- My hosted Azure Function container app belongs to the
DEMO-SUBSCRIPTION
- My hosted Azure Function container app belongs to the
-
I have defined the
Azure/functions-container-action@v1in a workflow so that it will take the image from the above registry and run it on the function app, but it keeps failing withResource xxx doesn't exist. -
In the debug logs, the call to
/subscriptions/is using theGLOBAL-SUBSCRIPTIONid above, not the app-specific one
-
Double-checking, I regenerated the service principal and pointed to the resource group containing the container app:
But the action still tries to GET using the other subscription above.
There doesn't seem to be a way to make this distinction, unless I'm doing something wrong?
Is the current assumption that both registry and container app need to be co-located within the same subscription?
- Dominant language
- JavaScript
- Stars
- 29
- Forks
- 20
- PR merge metrics
- No merged PRs in 30d
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
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/functions-container-action
-
need-to-triage
Difficulty 4/5 3-5 days Newbie friendliness 25/100
-
need-to-triage
Difficulty 4/5 3-5 days Newbie friendliness 25/100
Azure/functions-container-action#51 · 1 comment ·
All issues in Azure/functions-container-action
Similar issues
-
Mend: dependency security vulnerability untriaged
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
opensearch-project/security-dashboards-plugin#2543 ·
Maintainers usually reply within 1 day
-
[quality] refresh-radar-reports.yml runs on ubuntu-latest while every other job pins ubuntu-24.04Openagent/quality hive/hosted-available-lke648397-260827-5n31 quality testing
Difficulty 1/5 1-3 hours Newbie friendliness 90/100
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
godotengine/godot-website#1432 ·
-
Add: Mooz RetroOpenchannels:add check:passed
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
Maintainers usually reply within 2 days
-
Difficulty 1/5 Under an hour Newbie friendliness 90/100
Maintainers usually reply within 1 day