Releases: spinnaker/echo
Releases · spinnaker/echo
echo 2.0.0-rc.4+springBoot2
chore(dependencies): move allthethings to implementation scope Transitive dependencies from api scope were causing badness in intellij. Marking all the things implementation as a starting point resolved the issue. Also fixed a couple of deprecation warnings
echo 2.0.0-rc.6+springBoot2
Merge remote-tracking branch 'upstream/master' into boot2
echo 1.602.0
feat(gcb): Notify igor of GCB builds
fix(triggers): avoid single event causing >1 executions of same pipeline
chore(triggers): add application and pipeline fields to Trigger
echo 1.601.6
- feat(auth): Propagate
X-SPINNAKER-ACCOUNTS
when triggering pipelines (#530)
echo 1.601.5
v1.601.5 chore(dependencies): Autobump spinnaker-dependencies (#528)
echo 1.601.4
fix(triggers): prevent double-triggering for pipelines with >1 triggers
echo 1.601.3
perf(triggers): index triggers based on type
Echo 1.601.2
v1.601.2 feat(declarative): changed Keel endpoint URL
echo 1.601.1
fix(pubsub): Don't log all pubsub events (#524) We're now logging all pubsub events in AbstractNotificationAgent; given the volume of these events, turn off this logging for pubsub.
echo 1.601.0
refactor(pubsub): Encapsulate logic for creating events (#523) * feat(pubsub): Send pubsub events through eventPropagator Currently all pubsub events are sent directly to the trigger event listener, rather than to the general eventPropagator (which notifies all event listeners). This means that pubsub events can never do anything other than start pipelines. (Other incoming events, such as webhooks or build notifications are sent to the general eventPropagator.) In order to allow pubsub messages to do other things than start pipelines, send the resulting event to the eventPropagator so that other listeners can act on these events. * refactor(pubsub): Encapsulate logic for creating events The logic for extracting artifacts from pubsub events and for creating events from the message is embedded in the logic for handling these messages. In order to allow more general events to be created from pubsub messages, create an interface EventCreator that handles creating an event from a pubsub MessageDescription. The initial implementation of EventCreator will extract artifacts and create exactly the same event as prior to this change, allowing us to remove the code from the pubsub subscribers and handler. When setting up a subscription it is now possible to pass in a custom EventCreator so that messages read from that subscription create arbitrary event types.