Open iMicknl opened 1 year ago
Can you try these options in the following order and let us know which one worked for you:
--no-use-keychain
. For instance: swa deploy --no-use-keychain
.--app-name
and --resource-group
--client-id
, --client-secret
, --app-name
and --resource-group
.Please let us know which option worked for you so we can update the docs.
@manekinekko what is the intended audience of the deploy command? I am migrating from 0.x to 1.x and using swa deploy
on CodeSpaces is giving me a hard time.
swa deploy -d token
, I bump into a size limit. Removing "azure-functions-core-tools": "^4.x",
. from my devDependencies solves this, but not my desired solution.swa deploy --no-use-keychain
seems to work, but while choosing the tenant it won't provide me the name. Only the tenant id. Choosing the tenant requires me to log in again and then it seems to work. (until it tells me that it is linked to GitHub, even though the previous deployment to preview worked via swa deploy -d token
.swa deploy -d token
again works and deploys the same version to preview. (it does not run / prompt for swa build first, thus I forgot). Running swa build
and swa deploy -d token
works with the newest version now.I would say that this CLI would especially be targetted for devs, for example using CodeSpaces, without having to do a lot of extra steps. Having an easy way to deploy a sample they download from GitHub, without configuring CI/CD etc. Is the feedback above valuable / already known?
Regarding this issue, option 2 seems to work (without providing the app name and resource group by the way).
Hey, is there any update on this? Trying to run swa cli inside a Github Codespace and this seems to be needed for login / deploy etc. It would be great to add a section on Codespaces / devcontainers and SWA tool to the docs, documenting the setup, port forwarding etc..
Before filing this issue, please ensure you're using the latest CLI by running
swa --version
and comparing to the latest version on npm.Are you accessing the CLI from the default port
:4280
?--port
) and accessing the CLI from that port:4280
ℹ️ NOTE: Make sure to enable debug logs when running any
swa
commands using--verbose=silly
Describe the bug When running
swa deploy
on GitHub Codespaces, I face the following error.✖ Cannot autolaunch D-Bus without X11 $DISPLAY
. This is not documented, so I am not sure what I miss and if GitHub Codespaces is just not supported.To Reproduce Steps to reproduce the behavior:
npx swa deploy
Expected behavior Deployment using the credentials of Azure CLI, where I am already logged in with.
Desktop (please complete the following information):
Additional context