Closed turesheim closed 1 year ago
Thanks for your input, we'll discuss it in next refinement meeting and come back to you
We have reviewed this (better late than never....) now. The package request does not contain enough info for Radix to cover this. :-) We recommend use rx (our Radix CLI). Closing this
In an attempt to get around issue #280 I have set up a GitHub Action to build the image we need and publish this to the repository's Docker registry. The idea was then to get Omnia Radix to use this private image registry to set up a new application instance. This works just fine, however I would like Omnia Radix to automatically pull and build only after the new image has been built by the GitHub Action so the event selected for the webhook is packages instead of push. This results in an error 400.
To Reproduce Steps to reproduce the behavior:
Expected behavior No error should be return and a new Radix build job should start after a new package has been published.
Application name in Radix
sima-runtime-example
Application component If applicable, add the name of the specific component(s) that fail
Cluster
Additional context Failing request header:
Failing payload: