Azure / Azure/ng-deploy-azure

Skip build and deploy directly is not working as described

Open
#100 1 comment 0 reactions 0 assignees View on GitHub
Dominant language
TypeScript
Stars
79
Forks
47
PR merge metrics
No merged PRs in 30d

Description

I'd like to avoid building automatically and deploying directly from a path, ideally I'd like to get an error if the path to be deployed is not existing or empty.

So I followed what is described in the README:

> Another option is to skip build, and deploy directly from a specific location. To do this, delete the target and configuration from azure.json, and provide a path with a value relative to the root of the project.

Prequisite: I first built with the configuration I need & "ng add ng-deploy-azure" run

If I only add "path", "ng run hello-world:deploy" is deploying without building as expected:

Example azure.json
> {
> "hosting": [
> {
> "app": {
> "project": "hello-world",
> "target": "build",
> "configuration": "production"
> "path": "public/static/hello-world"
> },
> "azureHosting": {
> ...
> }
> }
> ]
> }

But if I follow exactly what is described, I mean removing target & config, to avoid the automatic build, I got the following error message:

> Error when trying to deploy:
> Azure hosting config is missing some details. Please run "ng add ng-deploy-azure" and select a storage account.

Example azure.json
> {
> "hosting": [
> {
> "app": {
> "project": "hello-world",
> "path": "public/static/hello-world"
> },
> "azureHosting": {
> ...
> }
> }
> ]
> }

I'd like to know what should I keep and what I can remove from this file to achieve my goal : deploying without building and getting an error if the app has not been built before (path empty or not existing)?
I think that the README should be updated.
Thanks for your help

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.