feat: Akamai SDK example, rollup config, edgeKV logic #128
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…wiah/sc-203998/initial-rollup-setup
dariushar
requested review from
kinyoklion,
louis-launchdarkly and
yusinto
as code owners
|
This pull request has been linked to Shortcut Story #203998: Create rollup configuration for us to bundle the Akamai Edge SDK. |
dariushar
changed the title
…heir own custom feature store and updated semantic versioning for alpha release
mmrj
reviewed
Jun 1, 2023
Co-authored-by: Molly <molly.jones@launchdarkly.com>
…tial-rollup-setup
kinyoklion
reviewed
Jun 2, 2023
ldhenry
reviewed
Jun 2, 2023
kinyoklion
approved these changes
Jun 2, 2023
Merged
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR includes the changes for releasing the initial version of the SDK (alpha version).
We have decided to create two different SDKs. One for using the EdgeKV feature store and one allowing the user send a specific feature store they would like to use. We're doing this because Akamai is expecting a file called
edgekv_token.jsbut that file won't exists if the user decides to specify their feature store. To avoid trying to dynamically load theedgekv_token.jsfile, we have decided to split the SDK into two different packages.Akamai Updates:
BEGIN_COMMIT_OVERRIDE
fix: Initial alpha release of the SDK with support for external data store
END_COMMIT_OVERRIDE