Mirrors/unleash.unleash
1
0
Fork 0
mirror of https://github.com/Unleash/unleash.git synced 2024-12-28 00:06:53 +01:00
Code Issues Projects Releases Wiki Activity
1ccbce23de
unleash.unleash/website/docs/reference/sdks/index.md
Thomas Heartman 14e052b9ac
docs: auto-generate remaining server-side SDK docs (#2858) 
This PR builds on the preceding doc auto-generation PRs and generates
documentation for the remaining server-side SDKs.

## Why

Refer to https://github.com/Unleash/unleash/pull/2809 for more context
about generating SDK docs.

## What

-   Adds generation for the remaining server-side SDKs
- Moves generated docs from the `/reference/sdks` directory to
`/generated` directory.
- Makes sure that the URLs do not change because of the move by using
the `slug` frontmatter property.
- replaces relative github links in the markdown documents so that they
become absolute github links. (refer to the next section)
- Updates some image styling so that it doesn't apply to readme badges
(we don't need them using `display: block`)

### On link replacing:

This PR adds handling of links in the generated documentation.
Specifically, it changes links in one case:

Relative links to github. Links to code and other files in the
repository. These are prefixed with the repository's URL.

While this should work in most cases, it will fail in cases where the
links to the files are not on the repository's primary branch.
(typically main, but could also be "v3", for instance). In these cases,
the links will get a double branch in the URL and will fail. However, I
see no easy way around this (though suggestions are definitely
accepted!), and think it's a fair tradeoff. It takes the links from
"definitely failing" to "will work in the vast majority of cases".

Note: I originally also wanted to handle the case where the link is an
absolute link to docs.getunleash.io. We could turn these into relative
urls to avoid full page reloads and enjoy a smoother experience.
However, the client-side redirects don't work correctly if the relative
URL goes to a redirect page, so you end up with a 404 page. As such, I
think it's better to leave the links as absolute for now.
2023-01-13 12:40:28 +01:00

11 KiB
Raw Blame History

title
SDK overview

In order to connect your application to Unleash you will need a client SDK (software developer kit) for your programming language and an API token. The SDK will handle connecting to the Unleash server instance and retrieving feature toggles based on your configuration. All versions of Unleash (OSS, Pro, and Enterprise) use the same client SDKs.

Unleash provides official client SDKs for a number of programming language. Additionally, our community have developed and contributed SDKs for other languages. So if you can't find your favorite language in the list of official SDKs, check out the list of clients written by our fantastic community.

Official SDKs

Server-side SDKs:

Server-side clients run on your server and communicate directly with your Unleash instance. We provide these official clients:

Client-side SDKs

Client-side SDKs can connect to the Unleash Proxy or to the Unleash front-end API, but not to the regular Unleash client API.

Server-side SDK compatibility table

The below table shows what features the various server-side SDKs support. Note that certain features make sense only for some clients due to how the programming language works or due to how the client works.

Legend:

  • ✅: Implemented
  • ⭕: Not yet implemented, but we're looking into it
  • ❌: Not implemented, not planned
  • N/A: Not applicable to this SDK

:::note

If you see an item marked with a ❌ that you would find useful, feel free to reach out to us (on Slack, for instance) with your use case. It may not be something we can prioritize right now, but if you'd like to contribute it back to the community, we'd love to help you build it.

:::

Capability Java Node.js Go Python Ruby .NET PHP Rust Unleash Proxy
Category: Initialization
Async initialization ✅ ✅ ✅ ✅ ✅ ✅ ❌ ✅ N/A
Can block until synchronized ✅ ✅ ✅ ⭕ ⭕ ✅ ✅ ⭕ N/A
Default refresh interval 10s 15s 15s 15s 15s 30s 30s 15s 5s
Default metrics interval 60s 60s 60s 60s 60s 60s 30s 15s 30s
Context provider ✅ N/A N/A N/A N/A ✅ ✅ N/A N/A
Global fallback function ✅ ✅ ✅ ✅ ❌ ❌ ❌ ❌ N/A
Toggle Query: namePrefix ✅ ✅ ❌ ❌ ❌ ❌ ✅ ❌ ✅
Toggle Query: tags ✅ ✅ ❌ ❌ ❌ ❌ ✅ ❌ ✅
Toggle Query: project_name ✅ ✅ ✅ ✅ ✅ ✅ N/A ⭕ ✅
Category: Custom Headers
static ✅ ✅ ✅ ✅ ✅ ✅ ✅ ⭕ N/A
function ✅ ✅ ⭕ ✅ ✅ (4.3) ✅ ✅ ⭕ N/A
Category: Built-in strategies
Standard ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅
Gradual rollout ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅
Gradual rollout: custom stickiness ✅ ✅ ✅ ✅ ✅ ✅ ✅ ⭕ ✅
UserID ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅
IP ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅
IP: CIDR syntax ✅ ✅ ✅ ✅ ✅ ⭕ ✅ ✅ ✅
Hostname ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅
Category: Custom strategies
Basic support ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅
Category: Strategy constraints
Basic support (IN, NOT_IN operators) ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅
Advanced support (Semver, date, numeric and extended string operators) (introduced in) ✅ (5.1) ✅ (3.12) ✅ (3.3) ✅ (5.1) ✅ (4.2) ✅ (2.1) ✅ (1.3.1) ⭕ ✅ (0.8)
Category: Unleash Context
Static fields (environment, appName) ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅
Defined fields ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅
Custom properties ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅
Category: isEnabled
Can take context ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅
Override fallback value ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅
Fallback function ✅ ✅ ✅ ✅ ✅ ⭕ ⭕ ⭕ ✅
Category: Variants
Basic support ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅
Custom fallback variant ✅ ✅ ✅ ✅ ✅ ✅ ✅ ⭕ ✅
Custom weight ✅ ✅ ✅ ✅ ✅ ✅ ✅ ⭕ ✅
Custom stickiness (beta) ✅ ✅ ✅ ✅ ✅ ✅ ✅ ⭕ ✅
Category: Local backup
File based backup ✅ ✅ ✅ ✅ ✅ ✅ ✅ ⭕ ✅
Category: Usage metrics
Can disable metrics ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅
Client registration ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅
Basic usage metrics (yes/no) ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅ ✅
Impression data ⭕ ✅ ⭕ ⭕ ⭕ ⭕ ✅ ⭕ ✅
Category: Bootstrap (beta)
Bootstrap from file ✅ ✅ ✅ ⭕ ✅ ✅ ✅ ⭕ ✅
Custom Bootstrap implementation ✅ ✅ ✅ ⭕ ✅ ✅ ✅ ⭕ ✅

Community SDKs ❤️

Here's some of the fantastic work our community has done to make Unleash work in even more contexts. If you still can't find your favorite language, let us know and we'd love to help you create the client for it!

Implement your own SDK

If you can't find an SDK that fits your need, you can also develop your own SDK. To make implementation easier, check out these resources:

  • Unleash Client Specifications - Used by all official SDKs to make sure they behave correctly across different language implementations. This lets us verify that a gradual rollout to 10% of the users would affect the same users regardless of which SDK you're using.
  • Client SDK overview - A brief, overall guide of the Unleash Architecture and important aspects of the SDK role in it all.

Working offline

Once they have been initialised, all Unleash clients will continue to work perfectly well without an internet connection or in the event that the Unleash Server has an outage.

Because the SDKs and the Unleash Proxy cache their feature toggle states locally and only communicate with the Unleash server (in the case of the server-side SDKs and the Proxy) or the Proxy (in the case of front-end SDKs) at predetermined intervals, a broken connection only means that they won't get any new updates.

Unless the SDK supports bootstrapping it will need to connect to Unleash at startup to get its initial feature toggle data set. If the SDK doesn't have a feature toggle data set available, all toggles will fall back to evaluating as disabled or as the specified default value (in SDKs that support that).

Bootstrapping

By default, all SDKs reach out to the Unleash Server at startup to fetch their toggle configuration. Additionally some of the server-side SDKs and the Proxy (see the above compatibility table) also support bootstrapping, which allows them to get their toggle configuration from a file, the environment, or other local resources. These SDKs can work without any network connection whatsoever.

Bootstrapping is also supported by the following front-end client SDKs: