question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

can not create app deployment after upgrading package to `arm-appplatform:2.1.0-beta.3`

See original GitHub issue
  • Package Name: @azure/arm-appplatform
  • Package Version: 2.1.0-beta.3
  • Operating system: Windows
  • nodejs
    • version: 16.16.0
  • browser
    • name/version:
  • typescript
    • version: 4.3.5
  • Is the bug related to documentation in

Describe the bug

Error (Invalid arguments: properties.source.relativePath cannot be empty., but I actually have specified relativePath as <default>) occurs when creating deployment for a basic tier app after upgrading package @azure/arm-appplatform to 2.1.0-beta.3. but it works well with @azure/arm-appplatform:2.0.0.

To Reproduce

  1. create an app (basic tier) without default deployment.
  2. create default deployment with code:
        let source: UserSourceInfoUnion | undefined;
        if (service.sku?.name?.toLowerCase().startsWith('e')) {
            source = { type: 'BuildResult', buildResultId: '<default>' };
        } else {
            source = { type: 'Jar', relativePath: '<default>', runtimeVersion: 'Java_11' };
        }
        const deployment: DeploymentResource = await this.client.deployments.beginCreateOrUpdateAndWait(service.resourceGroup, service.name, app.name, deploymentName, {
            properties: {
                source,
                deploymentSettings: {
                    resourceRequests: {
                        memory: '1Gi',
                        cpu: '1'
                    }
                },
            },
            sku: {
                capacity: 1,
                tier: 'Standard',
                name: 'S0',
            }
        });

Both the relativePath and runtimeVersion are removed at this step before sending request to server according to my investigation: image it’s looking for UserSourceInfo.Jar but there is only UploadedUserSourceInfo.Jar image

Expected behavior deployment is created successfully.

Screenshots If applicable, add screenshots to help explain your problem.

Additional context I am updating Azure Spring Apps extension for VS Code, of which the repository is here https://github.com/microsoft/vscode-azurespringcloud. it works well to create app in branch main but NG in branch wangmi/dev, the only change is upgrading the package.

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:8 (5 by maintainers)

github_iconTop GitHub Comments

1reaction
wangmingliang-mscommented, Oct 10, 2022

sounds good, thanks.

1reaction
qiaozhacommented, Oct 10, 2022

We can upgrade the version in our next release. As ^1.5.0 will automatically take the latest version of @azure/core-client if there’s no package-lock.json in the customer side, we thought it’s okay to not update the core-client version right now.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Apply the latest platform update to environments | Dynamics 365
After the platform update package is in your LCS asset library, follow the flow to apply an update from the LCS environment page....
Read more >
Helm force with deployment doesn't update code #7192 - GitHub
I'm using Helm and the Helm Deploy task in Azure Pipelines (have ... Error: UPGRADE FAILED: cannot patch "my-app-dev-website-mhc-front" with ...
Read more >
Use MDM to deploy software updates to Apple devices
You can control how software updates and upgrades appear for supervised Apple devices enrolled in a mobile device management (MDM) solution.
Read more >
MSBuild deploy failing after upgrade to .NET 4.5
NET 4.5. We have a build script to deploy the application on the test server. We have two boxes - one is Windows...
Read more >
VMware Tanzu Application Service for VMs v2.9 Release Notes
Rolling App Deployment Does Not Timeout; Incompatible Stemcell Causes Job Failure; Run NFS Broker Errand Before Upgrade; Disable the Smoke Test Errand If ......
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found