OElesin / querypal

Web UI for Amazon Athena
Apache License 2.0
54 stars 26 forks source link

Error creating repo #3

Closed pavanparthasarathy closed 2 years ago

pavanparthasarathy commented 3 years ago

Hi @OElesin I'm getting the below error when I deploy. "ResourceStatusReason": "There was an issue setting up your repository. Please try again later.({\"message\":\"Not Found\",\"documentation_url\":\"https://docs.github.com/rest/reference/repos#create-a-repository-webhook\"}) (Service: Amplify; Status Code: 400; Error Code: BadRequestException; Request ID: ebeff70b-d562-4227-a7dd-ec21cda3b1fe; Proxy: null)",

dattajoshi commented 3 years ago

I'm facing this issue too..... Is there any update on this??

OElesin commented 3 years ago

@dattajoshi and @pavanparthasarathy,

I'm not sure why you are seeing this error, but I will assume that you need to setup a GitHub token required for a webhook .

Give this a try.

pavanparthasarathy commented 3 years ago

@OElesin I have setup the token, it fails post that step. image

OElesin commented 3 years ago

@pavanparthasarathy, thanks for sharing the screenshot. I looked at it and it appears that the right parameter for the Amplify App name i.e. QUERYPAL_AMPLIFY_NAME was not set properly. I made the changes and hopefully this should resolve it.

Please pull the latest changes and try again.

pavanparthasarathy commented 3 years ago

@OElesin I'm still getting the same error. Please find the screenshot image

tylerdelange commented 3 years ago

I was also really hoping to give this a try, but I am also getting the same error as above, and I do have my GitHub key set...


There was an issue setting up your repository. Please try again later.({"message":"Not Found","documentation_url":"https://docs.github.com/rest/reference/repos#create-a-repository-webhook"}) (Service: Amplify; Status Code: 400; Error Code: BadRequestException; Request ID: bda4d2b8-7d5a-4908-8862-d8b4f699ed42; Proxy: null)


OElesin commented 3 years ago

@tylerdelange , this is quite strange. It should have been solved. I'll have another look.

optus-leo commented 3 years ago

hi @OElesin , do you have any updates on this?

OElesin commented 2 years ago

Closing this as issue with deployment has been resolved in the newest updates. Kindly reopen if you still experience this.