search

Azure / container-apps-deploy-action

GitHub Action for building and deploying Azure Container Apps
MIT License
52 stars 29 forks source link

`ERROR: Bad Request`, HTTP Error 400. The request URL is invalid #78

Closed afifurrohman-id closed 9 months ago

afifurrohman-id commented 11 months ago

Description

I don't know about this error because i haven't made an HTTP request yet, i have checked my options and credentials but is correct and OK

Default ingress value: external
Default target port: 80
/usr/bin/az containerapp create -n unknown -g *** --environment personal-env
 --output none --registry-server ghcr.io --registry-username example --registry-password *** --ingress external --target-port 80 -i ghcr.io/example/example:c168b06254b66f47b2fef12c19df71234538c1ea
WARNING: The behavior of this command has been altered by the following extension: containerapp
ERROR: Bad Request(<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN""http://www.w3.org/TR/html4/strict.dtd">
<HTML><HEAD><TITLE>Bad Request</TITLE>
<META HTTP-EQUIV="Content-Type" Content="text/html; charset=us-ascii"></HEAD>
<BODY><h2>Bad Request - Invalid URL</h2>
<hr><p>HTTP Error 400. The request URL is invalid.</p>
</BODY></HTML>
)
Error: The process '/usr/bin/az' failed with exit code 1
Error: The process '/usr/bin/az' failed with exit code 1

Updated (5:54 PM - 26/11/2023)

This error not occur when already have container apps, but why not describe should create container apps? as docs say they can create container apps and update if already exists.

### Tasks
- [x] Try create container apps first
harryli0108 commented 9 months ago

Hi @afifurrohman-id I do apologize for the long-delayed reply. We've just merged the fix of this issue. the latest v2 should have the fix now.