Skip to content

Add SDK sample: batch deployment from a registry pipeline component - #4077

Merged
lavakumarrepala merged 18 commits into
mainfrom
copilot/fix-batch-registry-pipeline-sample
Jul 28, 2026
Merged

Add SDK sample: batch deployment from a registry pipeline component#4077
lavakumarrepala merged 18 commits into
mainfrom
copilot/fix-batch-registry-pipeline-sample

Conversation

@lavakumarrepala

@lavakumarrepala lavakumarrepala commented Jul 21, 2026

Copy link
Copy Markdown
Member

Description

Checklist

  • I have read the contribution guidelines.
  • I have coordinated with the docs team (mldocs@microsoft.com) if this PR deletes files or changes any file names or file extensions.
  • Pull request includes test coverage for the included changes.
  • This notebook or file is added to the CODEOWNERS file, pointing to the author or the author's team.

ICR : https://msdata.visualstudio.com/Vienna/_workitems/edit/4314321

achauhan-scc
achauhan-scc previously approved these changes Jul 23, 2026
@lavakumarrepala
lavakumarrepala marked this pull request as ready for review July 23, 2026 05:59
@saanikaguptamicrosoft

Copy link
Copy Markdown
Member

Nit: Please update the PR title to Add SDK sample: batch deployment from a registry pipeline component

@lavakumarrepala lavakumarrepala changed the title Copilot/fix batch registry pipeline sample Add SDK sample: batch deployment from a registry pipeline component Jul 27, 2026
lavakumarrepala and others added 5 commits July 27, 2026 09:39
Removed the pip install command for azure-ai-ml from the notebook.
Fixed JSON formatting issue by removing an extraneous comma.
… notebook

The notebook should validate against the CI-provided azure-ai-ml (dev-requirements, or the freshly-built release wheel via setup.sh), not downgrade to a pinned old SDK. Matches the sibling pipeline_with_components_from_yaml notebook, which has no install cell.

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Copilot-Session: 48bc14df-6a6c-4fb3-bb66-4b187cc8163e
…d ComponentDeployment.Enabled property

The endpoint used a fixed name and set properties={'ComponentDeployment.Enabled': True}.
On re-run, begin_create_or_update tried to update the existing endpoint's immutable
properties (also a True vs true case mismatch), failing with EndpointPropertiesUpdateNotSupported.
Match sibling notebooks (hello-batch, training-with-components): append a random suffix so a
fresh endpoint is created each run, and drop the unnecessary property (PipelineComponentBatchDeployment
works without it).

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Copilot-Session: 48bc14df-6a6c-4fb3-bb66-4b187cc8163e
@lavakumarrepala
lavakumarrepala merged commit ac287c8 into main Jul 28, 2026
7 checks passed
@lavakumarrepala
lavakumarrepala deleted the copilot/fix-batch-registry-pipeline-sample branch July 28, 2026 05:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants