Wrong deploy destination for static web app

Question

Wrong deploy destination for static web app

Jacky Lam 210

Hi,

Recently, I try to deploy my static web app by CLI like this:

swa deploy --app-name mystaticapp --env production ./dist/fuse

It runs successfully and show this in the output:

√ Project deployed to https://icy-plant-00c90ef1e.3.azurestaticapps.net

However, the endpoint of my static web app resource should be https://victorious-tree-05ba2ad00.3.azurestaticapps.net instead.

And I search around all the static web app I owned but none of them has endpoint started with icy-plant. I wonder where it comes from and how can I deploy to correct end point. Thanks.

Best Regards,

Jacky

SnehaAgrawal-MSFT 22,706 Reputation points Moderator

2023-07-27T15:39:19.3933333+00:00

@Jacky Lam Just checking if you have chance to see recent response. Please let us know if further query or issue remains.
Jacky Lam 210 Reputation points

2023-07-28T00:38:16.5433333+00:00

icy-plant is not automatically generated by static web app. It should be victorious-tree instead.
However, my problem is resolved. It turns out my deployment script has an unexpected line which trying to deploy to a preview environment but the line intended to deployed to production doesn't specify the environemnt explicitly. After fix that, everything works fine. However, it is curious to me where the icy-plant is coming from. Under my tenant, there is no such end point naming that.
Jacky Lam 210 Reputation points

2023-07-28T00:39:46.13+00:00

My problem is resolved. It is seems I haven't add the --env switch explicitly. But it is weird it use icy-plant which doesn't exist anywhere under my tenant.
SnehaAgrawal-MSFT 22,706 Reputation points Moderator

2023-08-03T08:59:51.66+00:00

@Jacky Lam Glad to know issue is resolved.

If you feel that my answer helped kindly accept as "Yes", so that you can help others in the community looking for remediation for similar issues.

Accepted answer

0 additional answers

Your answer

SnehaAgrawal-MSFT 22,706 Reputation points Moderator

2023-07-27T15:39:19.3933333+00:00

@Jacky Lam Just checking if you have chance to see recent response. Please let us know if further query or issue remains.
Jacky Lam 210 Reputation points

2023-07-28T00:38:16.5433333+00:00

icy-plant is not automatically generated by static web app. It should be victorious-tree instead.
However, my problem is resolved. It turns out my deployment script has an unexpected line which trying to deploy to a preview environment but the line intended to deployed to production doesn't specify the environemnt explicitly. After fix that, everything works fine. However, it is curious to me where the icy-plant is coming from. Under my tenant, there is no such end point naming that.
Jacky Lam 210 Reputation points

2023-07-28T00:39:46.13+00:00

My problem is resolved. It is seems I haven't add the --env switch explicitly. But it is weird it use icy-plant which doesn't exist anywhere under my tenant.
SnehaAgrawal-MSFT 22,706 Reputation points Moderator

2023-08-03T08:59:51.66+00:00

@Jacky Lam Glad to know issue is resolved.

If you feel that my answer helped kindly accept as "Yes", so that you can help others in the community looking for remediation for similar issues.

Answer 1

@Jacky Lam Thanks for reaching here!

It's possible that the endpoint name "icy-plant-00c90ef1e" was automatically generated by Azure Static Web Apps during the deployment process.

You may deploy using a swa-cli.config.json configuration file in your project and have a single configuration entry.

{
  "configurations": {
    "my-app": {
      "appLocation": "./",
      "apiLocation": "api",
      "outputLocation": "frontend",
      "start": {
        "outputLocation": "frontend"
      },
      "deploy": {
        "outputLocation": "frontend"
      }
    }
  }
}

Then you can deploy your application by running the following steps:

If your front-end application requires a build step, run swa build or refer to your application build instructions.
Deploy your app: swa deploy
If you have multiple configuration entries, you can provide the entry ID to specify which one to use: swa deploy my-otherapp

Note that the path for outputLocation must be relative to the appLocation.

Check for the options you use with swa deploy.

Let us know.

Share via

Wrong deploy destination for static web app

0 additional answers

Your answer