0.3.0

This release is compatible with keptn 0.8.0 - 0.8.3

New Features

• Refactored service to now act as an action provider that can be integrated into the keptn remediation config workflow.
• Service is now subscribed to sh.keptn.event.action.triggered events.
• Able to directly interact with the ServiceNow REST API trigger
• Use CloudEvents 1.0
• Removed deprecated event broker
• Move Build and Tests from Travis-CI to GH Actions

0.2.1

Release Notes 0.2.1

New Features:

• Made namespace of service configurable
• Deploy distributor as a sidecar of the service within the same pod

0.2.0

Release Notes 0.2.0

This release is compatible with Keptn release 0.6.0.

The service is designed to receive problem events from keptn and create incidents in ServiceNow. In this release, the service is capable of:

• create/update events and alerts in ServiceNow and assign them a specific user

To trigger these actions, the service listens to CloudEvents from type:

• sh.keptn.event.problem.open: When receiving this event, an alert is either created or updated

0.1.4

Release Notes 0.1.4

New Features

• Use new logging format #535

Fixed Issues

Known Limitations

0.1.3

Release Notes 0.1.3

New Features

• Change of deployment and service manifest from Knative to Kubernetes resources

Fixed Issues

• Update of npm dependencies

0.1.2

Release Notes 0.1.2

Fixed Issues

• Upgrade of axios package version to 0.19.0 #413

0.1.1

Release Notes 0.1.1

New Features

• Scripts for use case reflect the change of the namespace name that now has the project name as prefix, e.g., sockshop-dev, sockshop-production #229

Fixed Issues

• Hard-coded URLs for Dynatrace SaaS tenants are removed to also support Dynatrace-managed tenants #255
• Set visibility of service to cluster-local #396

0.1.0

This release is compatible with keptn release 0.2.0.

The service is designed to receive problem events from keptn and create incidents in ServiceNow. In this release, the service is capable of:

• create incidents in ServiceNow and assign them a specific user
• update incidents in ServiceNow once they have been resolved

To trigger these actions, the service listens to CloudEvents from type:

• sh.keptn.events.problem: When receiving this event, an incident is either created or updated.