Skip to content

[Key Vault] Added API 2026-07-01-preview with EKM Private Endpoint support - #48963

Draft
Nicola Camillucci (ncamillucci) wants to merge 4 commits into
mainfrom
ncamillucci/ekm-pe-private
Draft

[Key Vault] Added API 2026-07-01-preview with EKM Private Endpoint support#48963
Nicola Camillucci (ncamillucci) wants to merge 4 commits into
mainfrom
ncamillucci/ekm-pe-private

Conversation

@ncamillucci

Copy link
Copy Markdown
Member

Description

Please add an informative description that covers that changes made by the pull request and link all relevant issues.

If an SDK is being regenerated based on a new API spec, a link to the pull request containing these API spec changes should be included above.

All SDK Contribution checklist:

  • The pull request does not introduce [breaking changes]
  • CHANGELOG is updated for new features, bug fixes or other significant changes.
  • I have read the contribution guidelines.

General Guidelines and Best Practices

  • Title of the pull request is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

  • Pull request includes test coverage for the included changes.

@azure-pipelines

Copy link
Copy Markdown
Azure Pipelines:
Successfully started running 1 pipeline(s).
10 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

@github-actions

This comment has been minimized.

@github-actions

Copy link
Copy Markdown
Contributor
[Pilot] PR Pipeline Failure Analysis

What failed

The python - portalservices Azure Pipelines check failed on build
6824928
(job: Build Analyze,
logs).

The automated azsdk ci analyze run for this PR could not retrieve any pipeline log or test-result
data for this build — both azure_pipeline_analyses and github_workflow_analyses came back empty,
and no failed test artifacts were found. This means the failure details (which step/task failed and
why) could not be extracted automatically; the analysis stopped at the check-run summary level.

Relevant pipeline output
{
  "azure_pipeline_analyses": [],
  "github_workflow_analyses": [],
  "failing_pull_request_checks": [
    {
      "name": "python - portalservices",
      "conclusion": "FAILURE",
      "details_url": "https://dev.azure.com/azure-sdk/590cfd2a-581c-4dcb-a12e-6568ce786175/_build/results?buildId=6824928",
      "app_name": "Azure Pipelines",
      "type": "CheckRun"
    },
    {
      "name": "python - portalservices (Build Analyze)",
      "conclusion": "FAILURE",
      "details_url": "https://dev.azure.com/azure-sdk/590cfd2a-581c-4dcb-a12e-6568ce786175/_build/results?buildId=6824928&view=logs&jobId=36df4387-3551-57fa-098c-b43a23930261",
      "app_name": "Azure Pipelines",
      "type": "CheckRun"
    }
  ],
  "operation_status": "Succeeded"
}

Recommended next steps

The workflow does not have the user's Azure DevOps identity and cannot access the internal
"python - portalservices" pipeline logs/test artifacts needed to diagnose the root cause. Please
analyze the pipeline by running this command locally while authenticated to Azure DevOps:

azsdk ci analyze https://github.com/Azure/azure-sdk-for-python/pull/48963 --output json

Copilot detected the failing pipeline and generated the analysis above. To have it attempt a
fix automatically, reply with @copilot please fix the failing pipeline on this PR.

Generated by Pipeline Analysis Next Steps · auto · 61.6 AIC · ⌖ 2.97 AIC · ⊞ 9.2K ·

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

Status: Untriaged

Development

Successfully merging this pull request may close these issues.

1 participant