You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
CloudBuildTrigger has trouble updating after v1.33.0 #357
hi @tonybenchsci can you let me know how this resource was created, did you "acquire" a resource and it had 'push' defined? Or did you specify the full resource with push and deleted it and added pullRequest?
Hi @spew, the full resource was created with github.push at first (status UpToDate). We tried to change it to github.pullRequest, which led to the error. I think it was working before (we upgraded from 1.26.0 to 1.33.0)
Thanks for the information @tonybenchsci . Was it created with github.push via config connector? That is to say the resource was entirely created and managed through config connector and you managed to reach this state?
Activity
spew commentedon Dec 28, 2020
Hi @tonybenchsci thanks for reporting this, we will work on reproducing and let you know.
spew commentedon Dec 28, 2020
hi @tonybenchsci can you let me know how this resource was created, did you "acquire" a resource and it had 'push' defined? Or did you specify the full resource with push and deleted it and added pullRequest?
tonybenchsci commentedon Jan 6, 2021
Hi @spew, the full resource was created with
github.pushat first (status UpToDate). We tried to change it togithub.pullRequest, which led to the error. I think it was working before (we upgraded from 1.26.0 to 1.33.0)spew commentedon Jan 6, 2021
Thanks for the information @tonybenchsci . Was it created with github.push via config connector? That is to say the resource was entirely created and managed through config connector and you managed to reach this state?
tonybenchsci commentedon Jan 8, 2021
@spew Yes it was created initially with KCC as well. We pretty much use it for our entire GCP infra across multiple projects :)
spew commentedon Jan 8, 2021
Thank you, we will be taking a look at this one.
jcanseco commentedon Mar 22, 2022
Hello all, we recently fixed this in KCC 1.78.0. Closing.