Skip to content

Docs: change default package source override to Dev feed#49490

Open
danieljurek wants to merge 1 commit into
mainfrom
djurek/docs-use-cfs
Open

Docs: change default package source override to Dev feed#49490
danieljurek wants to merge 1 commit into
mainfrom
djurek/docs-use-cfs

Conversation

@danieljurek

Copy link
Copy Markdown
Member

Generates the onboarding file with the dev feed as the default URL.

DEPENDS ON migration of legacy packages to use

"packageDownloadUrl": "https://repo1.maven.org/maven2"

in their metadata JSONs if the package does not exist in the Dev Feed (i.e. mostly legacy or packages that ship outside of the Azure SDK EngSys)

@danieljurek danieljurek self-assigned this Jun 12, 2026
Copilot AI review requested due to automatic review settings June 12, 2026 19:14

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the Java docs onboarding generation to default to the Azure SDK public DevOps Maven feed, removing the explicit daily-docs override so the pipeline relies on the script’s default package source.

Changes:

  • Change the default packageDownloadUrl in Docs-Onboarding.ps1 from Maven Central to the Java public dev feed.
  • Remove the -PackageSourceOverride argument from the daily docs onboarding step in eng/pipelines/docindex.yml.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
eng/scripts/docs/Docs-Onboarding.ps1 Switches the default onboarding package source to the public dev feed.
eng/pipelines/docindex.yml Stops passing an explicit daily-docs package source override (now relies on script default).
Comments suppressed due to low confidence (1)

eng/scripts/docs/Docs-Onboarding.ps1:35

  • With the default package source now pointing to the DevOps feed, packages that only exist on Maven Central will need a per-package override. However, this function currently ignores a top-level packageDownloadUrl value in the metadata (it always uses the global default unless DocsCiConfigProperties overwrites it). If the docs metadata JSONs are updated as described in the PR to include "packageDownloadUrl": "https://repo1.maven.org/maven2", that override will be silently ignored and those packages will still be onboarded against the dev feed.
    $packageDownloadUrl = 'https://pkgs.dev.azure.com/azure-sdk/public/_packaging/azure-sdk-for-java/maven/v1'
    if ($PackageSourceOverride) {
        $packageDownloadUrl = $PackageSourceOverride
    }

    $onboardedPackages = @()
    foreach ($package in $metadata) {

        $packageInfo = [ordered]@{
            packageArtifactId = $package.Name
            packageGroupId = $package.Group
            packageVersion = $package.Version
            packageDownloadUrl = $packageDownloadUrl
        }

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.

2 participants