Azure / Azure/static-web-apps

Current directory cannot be identical to or contained within artifact folders [Windows only]

Open
#1,672 2 comments 0 reactions 0 assignees View on GitHub
Dominant language
No language data
Stars
346
Forks
67
PR merge metrics
No merged PRs in 30d

Description

Start from an empty folder and have one html and one js file (content really does not matter)
For example:

Image

then run swa-cli init and create the config file using static html and app code and output as "."
like:

```json
{
"$schema": "https://aka.ms/azure/static-web-apps-cli/schema",
"configurations": {
"test1": {
"appLocation": ".",
"outputLocation": ".",
}
}
}
```

Then run swa-cli deploy.
Notice how the cli completes w/o returning any error but the SWA in the azure portal stay in Uploading state forever:

Image

** Debug:
If you run `swa-cli deploy -V silly` , you can see almost at the end:

```
ℹ Current directory cannot be identical to or contained within artifact folders.
ℹ For further information, please visit the Azure Static Web Apps documentation at https://docs.microsoft.com/en-us/azure/static-web-apps/
ℹ If you believe this behavior is unexpected, please raise a GitHub issue at https://github.com/azure/static-web-apps/issues/
```

So, apparently the SWA service is finding an issue about directories can't be the same but the swa-cli is not making this an error back to the user. Making it a silent bug.
But the SWA service is neither making the state to be an error... Instead, it gets stock in Uploading state.

** Expected

the swa-cli should return an error and the SWA service should display an error state

** More debug notes

When trying this issue in linux, the swa-cli returns the error as expected:

Image

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.