Skip to content

Releases: IBM/event-notifications-go-admin-sdk

v0.12.0

23 Dec 13:29
Compare
Choose a tag to compare

0.12.0 (2024-12-23)

Features

v0.11.0

30 Oct 04:11
Compare
Choose a tag to compare

0.11.0 (2024-10-30)

Features

v0.10.0

04 Oct 05:30
Compare
Choose a tag to compare

0.10.0 (2024-10-04)

Features

v0.9.0

04 Sep 04:46
Compare
Choose a tag to compare

0.9.0 (2024-09-04)

Features

v0.8.0

09 Aug 09:36
Compare
Choose a tag to compare

0.8.0 (2024-08-09)

Features

  • SMTP allowed IP Update unsupported, Metrics Feature enabled (#56) (cd62de9)

BREAKING CHANGE

  • SMTP allowed IP Update unsupported

v0.7.0

29 Jul 07:46
Compare
Choose a tag to compare

0.7.0 (2024-07-29)

Features

v0.6.1

15 May 05:15
Compare
Choose a tag to compare

0.6.1 (2024-05-15)

Bug Fixes

v0.6.0

26 Apr 05:50
Compare
Choose a tag to compare

0.6.0 (2024-04-26)

BREAKING CHANGE

Struct TemplateConfig is changed to TemplateConfigOneOfEmailTemplateConfig for email and TemplateConfigOneOfSlackTemplateConfig for slack.

FEATURES

Slack Template

customize Slack notifications sent through EN so they are more relevant, actionable, and aligned with specific use cases and workflows.

  • User can apply a pre-defined template to the Slack destination.
  • Template supports dynamic substitution.
  • Use can type or paste template when creating a subscription.
  • User can upload a template.

SMTP

Access EN email SMTP server directly using SMTP protocol so that we can use email integrations that are built in to 3rd party software tools that I need for my application or environment.

FIX

  • Vulnerability fixes.

smtp slack template and vulnerability fix (#53) (f4fb4ed)

v0.5.0

01 Mar 05:20
Compare
Choose a tag to compare

0.5.0 (2024-03-01)

Features

  • support of Jobs in code engine destination (#52) (fe50776)

code engine destination is added with two options now, one with application type and another option with job where we can trigger the jobs.

Braking changes

While creating and updating code engine destination DestinationConfigOneOfWebhookDestinationConfig was used to specify the destination configurations as both webhook and code engine destintations had common properties.
As introducing job and application type in to code engine destination hence creating a separate struct for code engine destination which is DestinationConfigOneOfCodeEngineDestinationConfig.
Users will have to use DestinationConfigOneOfCodeEngineDestinationConfig instead of DestinationConfigOneOfWebhookDestinationConfig for specifying destination configurations.

v0.4.1

29 Jan 15:06
Compare
Choose a tag to compare

0.4.1 (2024-01-29)

Bug Fixes