search

navicore / teams-notification-resource

for Concourse CI notifications on Microsoft Teams
MIT License
32 stars 33 forks source link

Bad payload received by generic incoming webhook #41

Open achille1789 opened 1 year ago

achille1789 commented 1 year ago

Hi, I tried to use your resource today for the first time and I am getting: error code 400 - Bad payload received by generic incoming webhook I am running your test pipeline with my webhook url. I tried to use my webhook on Postman and it worked. I saw that you recently closed a similar issues, so as you suggested there, I tried to use tag v0.9.9 instead of "latest" but Concourse shows this error "version is missing from previous step". I tried also to use v0.9.7 but I am getting the same error code 400.

Do you have any suggestion? Thanks

navicore commented 1 year ago

The 400 error will come from any build earlier than v0.9.9 so you need to use that tag or a fresh pull of "latest". I suspect you have a cached copy of an older image under the "latest" tag.

When you got the error changing to v0.9.9, did you change the resource type def?

resource_types:

- name: teams-notification
  type: docker-image
  source:
    repository: navicore/teams-notification-resource
    tag: v0.9.9

If you still get 400 http errors after using v0.9.9 then you've encountered a new bug and we'll work on that but so far everyone that has hit the 400 error has seen it fixed with v0.9.9.

achille1789 commented 1 year ago

Hi thanks for the quick reply. I don't think I had a cached copy because I tried for the first time today to use your resource and I started using "latest". Regarding your question, yes I set "tag: v0.9.9" and I got "version is missing from previous step" where instead setting "tag: latest" or "tag: v0.9.7" the task runs but I get 400 error.

Thanks for your support

navicore commented 12 months ago

@achille1789 I wonder if this is an issue that happens going from an earlier build to v0.9.9. I wonder if there is any way to ensure you are not resuming your pipeline when you make this change - the error makes it seem like there is some unfinished state.

Anyway - I will try to reproduce the error on my end and get back to you....