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
- README.md
- source code documentation
- SDK API docs on https://docs.microsoft.com
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
- create an app (basic tier) without default deployment.
- 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:
it’s looking for
UserSourceInfo.Jar
but there is only UploadedUserSourceInfo.Jar
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:
- Created a year ago
- Comments:8 (5 by maintainers)
sounds good, thanks.
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.