Skip to content

Latest commit

 

History

History
310 lines (219 loc) · 18.1 KB

CHANGELOG.md

File metadata and controls

310 lines (219 loc) · 18.1 KB
Raw

Changelog

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog and this project adheres to Semantic Versioning.

[4.1.0] - August 29, 2024

New Features

  • Moderate & high CVEs are fixed. (#414,#416)
  • Log levels are changed to Debug and redundant info logs are removed to make /decide API call less noisy. (#420)
  • isEveryoneElseVariation field is added in /decide API response. (#422)

[4.0.0] - January 22, 2024

New Features

The 4.0.0 release introduces a new primary feature, Advanced Audience Targeting enabled through integration with Optimizely Data Platform (ODP) (#356, #364, #365, #366).

You can use ODP, a high-performance Customer Data Platform (CDP), to easily create complex real-time segments (RTS) using first-party and 50+ third-party data sources out of the box. You can create custom schemas that support the user attributes important for your business, and stitch together user behavior done on different devices to better understand and target your customers for personalized user experiences. ODP can be used as a single source of truth for these segments in any Optimizely or 3rd party tool.

With ODP accounts integrated into Optimizely projects, you can build audiences using segments pre-defined in ODP. The SDK will fetch the segments for given users and make decisions using the segments. For access to ODP audience targeting in your Feature Experimentation account, please contact your Optimizely Customer Success Manager.

This version includes the following changes:

  • FetchQualifiedSegments() API has been added to the /decide endpoint. This API will retrieve user segments from the ODP server. The fetched segments will be used for audience evaluation. Fetched data will be stored in the local cache to avoid repeated network delays.

  • SendOdpEvent() API has been added with the /send-opd-event endpoint. Customers can build/send arbitrary ODP events that will bind user identifiers and data to user profiles in ODP.

For details, refer to our documentation pages:

This release also introduces a fundamental enhancement to the agent with the addition of a datafile syncer. This feature is designed to facilitate seamless synchronization of datafiles across agent nodes, ensuring consistency and accuracy in the operation of the webhook API. The datafile syncer uses a PubSub system (Default: Redis) to send updated datafile webhook notification to Agent nodes (in HA system) so that nodes can immediately fetch the latest datafile. (#405)

Breaking Changes

  • ODPManager in the SDK is enabled by default. Unless an ODP account is integrated into the Optimizely projects, most ODPManager functions will be ignored. If needed, ODPManager can be disabled when OptimizelyClient is instantiated. From Agent, it can be switched off from config.yaml or env variables.
  • Updated go-sdk version to v2.0.0 with module path github.com/optimizely/go-sdk/v2

Functionality Enhancement

  • Updated openapi schema to 3.1.0. (#392)
  • Added support for prometheus metrics. (#348)
  • Github Issue template is udpated. (#396)
  • Updated go version to 1.21. (#398)
  • Added OpenTelemetry Tracing Support. (#400)
  • Added traceID & spanID to logs. (#407)

Bug fixes

In previous versions, there was an issue where the Notification API would miss notification events when the Agent was operating in HA mode. It only got notification events from one Agent node. The bug has been addressed in this release with the implementation of a comprehensive solution. A PubSub system (Default: Redis) is used to ensure consistent retrieval of notification events across all nodes in an HA setup. (#399)

[3.2.0] - December 13, 2023

New Features

  • Added support for including traceId and spanId into the logs. (#407)

[3.1.0] - November 3, 2023

New Features

  • Added support for Prometheus-based metrics alongside expvar metrics. This can be configured from the config.yaml file. (#348)

  • Added support for OpenTelemetry tracing. Distributed tracing is also supported according to W3C TraceContext. (#400, #401, #402)

[4.0.0-beta] - May 11, 2023

New Features

The 4.0.0-beta release introduces a new primary feature, Advanced Audience Targeting enabled through integration with Optimizely Data Platform (ODP) (#356, #364, #365, #366).

You can use ODP, a high-performance Customer Data Platform (CDP), to easily create complex real-time segments (RTS) using first-party and 50+ third-party data sources out of the box. You can create custom schemas that support the user attributes important for your business, and stitch together user behavior done on different devices to better understand and target your customers for personalized user experiences. ODP can be used as a single source of truth for these segments in any Optimizely or 3rd party tool.

With ODP accounts integrated into Optimizely projects, you can build audiences using segments pre-defined in ODP. The SDK will fetch the segments for given users and make decisions using the segments. For access to ODP audience targeting in your Feature Experimentation account, please contact your Optimizely Customer Success Manager.

This version includes the following changes:

  • FetchQualifiedSegments() API has been added to the /decide endpoint. This API will retrieve user segments from the ODP server. The fetched segments will be used for audience evaluation. Fetched data will be stored in the local cache to avoid repeated network delays.

  • SendOdpEvent() API has been added with the /send-opd-event endpoint. Customers can build/send arbitrary ODP events that will bind user identifiers and data to user profiles in ODP.

For details, refer to our documentation pages:

Breaking Changes

  • ODPManager in the SDK is enabled by default. Unless an ODP account is integrated into the Optimizely projects, most ODPManager functions will be ignored. If needed, ODPManager can be disabled when OptimizelyClient is instantiated. From Agent, it can be switched off from config.yaml or env variables.

[3.0.1] - March 16, 2023

  • Update README.md and other non-functional code to reflect that this SDK supports both Optimizely Feature Experimentation and Optimizely Full Stack. (#369).

[3.0.0] - February 28, 2023

  • Upgrade golang version to 1.20 (#357).
  • Fix an issue with oauth/token API denying client access (#346).

Breaking Changes

  • Minimum required golang version for agent has been upgraded to 1.20 to fix vulnerabilities.

[2.7.1] - December 20, 2022

  • Add support for asynchronous Save using rest UPS by setting async boolean value inside config.yaml (#350).

[2.7.0] - April 6, 2022

  • Add UserProfileService support. Out of the box implementations include in-memory, rest and redis. In-memory service supports both fifo and lifo orders. For details refer to our documentation page: UserProfileService (#326, #331).
  • Add more detail in documentation for sdk key. (#332)
  • Add support to remove sdkKey from logs (#329).
  • Update JWT library to https://github.com/golang-jwt/jwt to fix security warnings since the previous library was no longer maintained (#334).

[2.6.0] - Jan 13, 2022

[2.5.0] - Sep 24, 2021

  • Add new fields (sdkKey, environmentKey, attributes, audiences, events, experimentRules, deliveryRules) to /config endpoint (PR #322):

[2.4.0] - March 3, 2021

New Features

[2.3.1] - November 17, 2020

  • Add "enabled" field to decision metadata structure

[2.3.0] - November 2, 2020

  • Introduce Agent interceptor plugins
  • Adding support for upcoming application-controlled introduction of tracking for non-experiment Flag decisions

[2.2.0] - October 5, 2020

  • Update to Optimizely Go SDK 1.4.0 with version audience condition evaluation based on semantic versioning as well as support for number 'greater than or equal to' and 'less than or equal to'.

[2.1.0] - September 23, 2020

  • For server.allowedHosts configuration property, add support for matching all subdomains of a host, or all hosts
  • Adding batching for agent (/v1/batch endpoint), including requests in parallel
  • Removed vulnerable version coreos/etcd

[2.0.0] - August 27, 2020

  • Add SDK key validation configuration
  • Reject request with invalid host (excluding port)
  • Block content type other than application/json
  • Introducing support for authenticated datafiles

Breaking Changes

  • Reject requests with invalid hosts, and introduce server.allowedHosts configuration property
  • Agent will now reject the request if the content-type is not specified from the clients
  • Add Host as a configurable item
    • Previously, Agent was listening on all interfaces, and did not allow configuring the network interface that it listens on. NewServer allowed specification of a port to listen on, but not an address.
    • Now, we have added configurable HOST, with the default value set to the localhost (127.0.0.1)
    • If there is a need to deploy Agent in docker, then the Host needs to be set to 0.0.0.0. This can be achieved by setting variable OPTIMIZELY_SERVER_HOST=0.0.0.0, or setting server.host to 0.0.0.0 in config file.

[1.3.0] - July 7th, 2020

  • Upgrade to use go-sdk v1.3.0. This adds support for JSON feature variables
  • Add /debug/pprof endpoints to the admin service
  • Run docker container as non root user
  • Log warnings when HTTPS and authorization are not enabled via configuration

[1.2.0] - June 18th, 2020

  • Expose event dispatch URL as a config parameter
  • Return experimentKey and variationKey with feature test decisions
  • Expose health endpoint for all listeners
  • Update API docs
  • Streamline CI stages

[1.1.0] - May 21st, 2020

  • Upgrade to use go-sdk 1.2.0. This adds support for multi-rule rollouts.

[1.0.2] - April 26th, 2020

  • Add datafileURLTemplate configuration option

[1.0.1] - April 22, 2020

  • Update to use go-sdk 1.1.3. This has a fix to the batch event processor was creating a dispatcher without a logger.

[1.0.0] - March 26th, 2020

  • Update documentation and examples
  • Add response body for override and track
  • Add userId in /activate response
  • Require userId in /activate request
  • Add python integration test suite
  • Add route handler and serve /openapi.yaml
  • Improve logging from the SDK

[0.14.0] - March 12th, 2020

  • Update windows build script
  • Remove pre-v1 api references
  • Allow unknown keys in /activate request
  • Improve API token issuer and auth client config
  • Expand on example python scripts and general documentation

[0.13.0] - March 5th, 2020

  • Add ability to blacklist TLS ciphers
  • Disable notifications and overrides by default
  • Update misc items in swagger spec
  • Improve README and add auth examples
  • Update SDK client config namespace
  • Add support for JWKS URI
  • Add OAuth to swagger spec
  • Add client secret creation tool

[0.12.0] - February 14th, 2020

  • Add support for typed user attributes
  • Add event-stream API for notifications
  • Add basic client credentials grant flow
  • Add native TLS support via configuration
  • Refactor to a POST based action API

[0.11.0] - January 17th, 2020

  • Bump to 1.0.0-rc1@d1b332c of the Optimizely go-sdk
  • Improve build tooling
  • Add standard metrics registry
  • Update documentation
  • Return 404 when feature or experiment are not found
  • Update event payloads to include Agent name and version

[0.10.0] - January 9th, 2020

  • Rename repo to optimizely/agent and update imports
  • Improve CI builds for Windows and SourceClear
  • Major /pkg refactoring
  • Exclude vulnerabilities identified through SourceClear

[0.9.0] - January 8th, 2020

  • Capture response time metrics in milliseconds
  • Bump to 1.0.0-rc1@d1b332c of the Optimizely go-sdk
  • Add metric visibility into event dispatcher
  • Miscellaneous clean-up and of docs and openapi spec
  • Add top level config package to consolidate configuration
  • Incorporate OptimizelyConfig into feature and experiment models
  • Add get experiment and list experiment endpoints
  • Add user features endpoint for batched decision responses
  • Add windows tooling
  • Add credit section to README
  • Improve service shutdown

[0.8.1] - December 4th, 2019

  • Bump to 1.0.0-rc1@973644b of the Optimizely go-sdk
  • Update test harness with new interface

[0.8.0] - November 18th, 2019

  • Adds ability to limit the number of active api connections
  • Allows SDK keys to be bootstrapped during startup
  • Adds http server timeouts
  • Adds graceful shutdown hooks
  • Adds support for forced variation API
  • Adds support for experimentation APIs

[0.7.0] - November 7th, 2019

  • Adds request timing metrics
  • Allows config file location to be set
  • Bumps go-sdk version to latest master

[0.6.0] - October 31st, 2019

  • Adds a few more debug logs
  • Updates to latest master to resolve some targeting issues
  • Update make clean to clean mod cache

Bug Fixes

  • Actually enable the impression tracking endpoint in the router

[0.5.0] - October 24th, 2019

  • Adds GET endpoint for user-based features
  • Adds impression tracking for Feature Tests

[0.4.0] - October 23rd, 2019

  • Adds admin endpoints for health, info and metrics
  • Adds requestId to logs and response header
  • Improves log integration with Optimizely SDK
  • Updates swagger spec to match current server implementation
  • Updates dependency version for the Optimizely SDK
  • Enhance webhook service configurability

[0.3.0] - October 14th, 2019

  • Adds user centric API routes
  • Introduces spf13/viper based configuration
  • Adds OptlyContext middleware
  • Adds webhook support for multiple concurrent SDK keys

[0.2.0] - October 3rd, 2019

  • Adds Optimizely webhook support
  • Adds full Feature MGMT support
  • Adds NSQ for UserEvent message transport
  • Adds support for multiple concurrent SDK keys

[0.1.0] - September 4th, 2019

This is the initial release which supported a basic web application and go-sdk integration.