-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Closed
Labels
Container AppsMgmtThis issue is related to a management-plane library.This issue is related to a management-plane library.Service AttentionWorkflow: This issue is responsible by Azure service team.Workflow: This issue is responsible by Azure service team.customer-reportedIssues that are reported by GitHub users external to the Azure organization.Issues that are reported by GitHub users external to the Azure organization.needs-team-attentionWorkflow: This issue needs attention from Azure service team or SDK teamWorkflow: This issue needs attention from Azure service team or SDK teamquestionThe issue doesn't require a change to the product in order to be resolved. Most issues start as thatThe issue doesn't require a change to the product in order to be resolved. Most issues start as that
Description
Package:
azure-mgmt-appcontainers==3.2.0
Problem
When using ContainerAppsAPIClient, the filter parameter for jobs_executions.list does not work. No matter what filter is provided, the following error is returned:
To Reproduce
from azure.identity import DefaultAzureCredential
from azure.mgmt.appcontainers import ContainerAppsAPIClient
container_apps_client = ContainerAppsAPIClient(
credential=DefaultAzureCredential(), subscription_id="xxxxxxxxxxxxx"
)
jobs_executions_list = container_apps_client.jobs_executions.list(
resource_group_name="my-rg",
job_name="container_app_job_name",
filter="name eq 'my-job-execution-name'",
)
for job in jobs_executions_list:
print(job)Expected Behavior
The results should be filtered server-side according to the filter expression.
Actual Behavior
An error is raised:
azure.core.exceptions.HttpResponseError: (InvalidParameterValue) The parameter filter has an invalid value.
Code: InvalidParameterValue
Message: The parameter filter has an invalid value.
Additional Information
- The REST API may not support filtering for this resource: [ContainerApps] Jobs executions - list encounters InternalServerError when parameter $filter added azure-rest-api-specs#26257
- Because filtering does not work, all job executions are retrieved (in my case, 400+), which significantly increases response time (6+ seconds) when only a single item is needed.
Impact
This limitation forces client-side filtering, which is inefficient and slow for large job histories.
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
Container AppsMgmtThis issue is related to a management-plane library.This issue is related to a management-plane library.Service AttentionWorkflow: This issue is responsible by Azure service team.Workflow: This issue is responsible by Azure service team.customer-reportedIssues that are reported by GitHub users external to the Azure organization.Issues that are reported by GitHub users external to the Azure organization.needs-team-attentionWorkflow: This issue needs attention from Azure service team or SDK teamWorkflow: This issue needs attention from Azure service team or SDK teamquestionThe issue doesn't require a change to the product in order to be resolved. Most issues start as thatThe issue doesn't require a change to the product in order to be resolved. Most issues start as that