@ezghcloud/flags-openfeature 0.0.0-stage → 1.0.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/LICENSE +201 -0
- package/README.md +167 -2
- package/dist/server.d.ts +42 -0
- package/dist/server.js +398 -0
- package/dist/shared/evaluator.d.ts +33 -0
- package/dist/shared/evaluator.js +111 -0
- package/dist/shared/http.d.ts +16 -0
- package/dist/shared/http.js +53 -0
- package/dist/shared/sse.d.ts +16 -0
- package/dist/shared/sse.js +128 -0
- package/dist/web.d.ts +44 -0
- package/dist/web.js +503 -0
- package/package.json +63 -4
package/LICENSE
ADDED
|
@@ -0,0 +1,201 @@
|
|
|
1
|
+
Apache License
|
|
2
|
+
Version 2.0, January 2004
|
|
3
|
+
http://www.apache.org/licenses/
|
|
4
|
+
|
|
5
|
+
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
|
|
6
|
+
|
|
7
|
+
1. Definitions.
|
|
8
|
+
|
|
9
|
+
"License" shall mean the terms and conditions for use, reproduction,
|
|
10
|
+
and distribution as defined by Sections 1 through 9 of this document.
|
|
11
|
+
|
|
12
|
+
"Licensor" shall mean the copyright owner or entity authorized by
|
|
13
|
+
the copyright owner that is granting the License.
|
|
14
|
+
|
|
15
|
+
"Legal Entity" shall mean the union of the acting entity and all
|
|
16
|
+
other entities that control, are controlled by, or are under common
|
|
17
|
+
control with that entity. For the purposes of this definition,
|
|
18
|
+
"control" means (i) the power, direct or indirect, to cause the
|
|
19
|
+
direction or management of such entity, whether by contract or
|
|
20
|
+
otherwise, or (ii) ownership of fifty percent (50%) or more of the
|
|
21
|
+
outstanding shares, or (iii) beneficial ownership of such entity.
|
|
22
|
+
|
|
23
|
+
"You" (or "Your") shall mean an individual or Legal Entity
|
|
24
|
+
exercising permissions granted by this License.
|
|
25
|
+
|
|
26
|
+
"Source" form shall mean the preferred form for making modifications,
|
|
27
|
+
including but not limited to software source code, documentation
|
|
28
|
+
source, and configuration files.
|
|
29
|
+
|
|
30
|
+
"Object" form shall mean any form resulting from mechanical
|
|
31
|
+
transformation or translation of a Source form, including but
|
|
32
|
+
not limited to compiled object code, generated documentation,
|
|
33
|
+
and conversions to other media types.
|
|
34
|
+
|
|
35
|
+
"Work" shall mean the work of authorship, whether in Source or
|
|
36
|
+
Object form, made available under the License, as indicated by a
|
|
37
|
+
copyright notice that is included in or attached to the work
|
|
38
|
+
(an example is provided in the Appendix below).
|
|
39
|
+
|
|
40
|
+
"Derivative Works" shall mean any work, whether in Source or Object
|
|
41
|
+
form, that is based on (or derived from) the Work and for which the
|
|
42
|
+
editorial revisions, annotations, elaborations, or other modifications
|
|
43
|
+
represent, as a whole, an original work of authorship. For the purposes
|
|
44
|
+
of this License, Derivative Works shall not include works that remain
|
|
45
|
+
separable from, or merely link (or bind by name) to the interfaces of,
|
|
46
|
+
the Work and Derivative Works thereof.
|
|
47
|
+
|
|
48
|
+
"Contribution" shall mean any work of authorship, including
|
|
49
|
+
the original version of the Work and any modifications or additions
|
|
50
|
+
to that Work or Derivative Works thereof, that is intentionally
|
|
51
|
+
submitted to Licensor for inclusion in the Work by the copyright owner
|
|
52
|
+
or by an individual or Legal Entity authorized to submit on behalf of
|
|
53
|
+
the copyright owner. For the purposes of this definition, "submitted"
|
|
54
|
+
means any form of electronic, verbal, or written communication sent
|
|
55
|
+
to the Licensor or its representatives, including but not limited to
|
|
56
|
+
communication on electronic mailing lists, source code control systems,
|
|
57
|
+
and issue tracking systems that are managed by, or on behalf of, the
|
|
58
|
+
Licensor for the purpose of discussing and improving the Work, but
|
|
59
|
+
excluding communication that is conspicuously marked or otherwise
|
|
60
|
+
designated in writing by the copyright owner as "Not a Contribution."
|
|
61
|
+
|
|
62
|
+
"Contributor" shall mean Licensor and any individual or Legal Entity
|
|
63
|
+
on behalf of whom a Contribution has been received by Licensor and
|
|
64
|
+
subsequently incorporated within the Work.
|
|
65
|
+
|
|
66
|
+
2. Grant of Copyright License. Subject to the terms and conditions of
|
|
67
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
68
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
69
|
+
copyright license to reproduce, prepare Derivative Works of,
|
|
70
|
+
publicly display, publicly perform, sublicense, and distribute the
|
|
71
|
+
Work and such Derivative Works in Source or Object form.
|
|
72
|
+
|
|
73
|
+
3. Grant of Patent License. Subject to the terms and conditions of
|
|
74
|
+
this License, each Contributor hereby grants to You a perpetual,
|
|
75
|
+
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
|
|
76
|
+
(except as stated in this section) patent license to make, have made,
|
|
77
|
+
use, offer to sell, sell, import, and otherwise transfer the Work,
|
|
78
|
+
where such license applies only to those patent claims licensable
|
|
79
|
+
by such Contributor that are necessarily infringed by their
|
|
80
|
+
Contribution(s) alone or by combination of their Contribution(s)
|
|
81
|
+
with the Work to which such Contribution(s) was submitted. If You
|
|
82
|
+
institute patent litigation against any entity (including a
|
|
83
|
+
cross-claim or counterclaim in a lawsuit) alleging that the Work
|
|
84
|
+
or a Contribution incorporated within the Work constitutes direct
|
|
85
|
+
or contributory patent infringement, then any patent licenses
|
|
86
|
+
granted to You under this License for that Work shall terminate
|
|
87
|
+
as of the date such litigation is filed.
|
|
88
|
+
|
|
89
|
+
4. Redistribution. You may reproduce and distribute copies of the
|
|
90
|
+
Work or Derivative Works thereof in any medium, with or without
|
|
91
|
+
modifications, and in Source or Object form, provided that You
|
|
92
|
+
meet the following conditions:
|
|
93
|
+
|
|
94
|
+
(a) You must give any other recipients of the Work or
|
|
95
|
+
Derivative Works a copy of this License; and
|
|
96
|
+
|
|
97
|
+
(b) You must cause any modified files to carry prominent notices
|
|
98
|
+
stating that You changed the files; and
|
|
99
|
+
|
|
100
|
+
(c) You must retain, in the Source form of any Derivative Works
|
|
101
|
+
that You distribute, all copyright, patent, trademark, and
|
|
102
|
+
attribution notices from the Source form of the Work,
|
|
103
|
+
excluding those notices that do not pertain to any part of
|
|
104
|
+
the Derivative Works; and
|
|
105
|
+
|
|
106
|
+
(d) If the Work includes a "NOTICE" text file as part of its
|
|
107
|
+
distribution, then any Derivative Works that You distribute must
|
|
108
|
+
include a readable copy of the attribution notices contained
|
|
109
|
+
within such NOTICE file, excluding those notices that do not
|
|
110
|
+
pertain to any part of the Derivative Works, in at least one
|
|
111
|
+
of the following places: within a NOTICE text file distributed
|
|
112
|
+
as part of the Derivative Works; within the Source form or
|
|
113
|
+
documentation, if provided along with the Derivative Works; or,
|
|
114
|
+
within a display generated by the Derivative Works, if and
|
|
115
|
+
wherever such third-party notices normally appear. The contents
|
|
116
|
+
of the NOTICE file are for informational purposes only and
|
|
117
|
+
do not modify the License. You may add Your own attribution
|
|
118
|
+
notices within Derivative Works that You distribute, alongside
|
|
119
|
+
or as an addendum to the NOTICE text from the Work, provided
|
|
120
|
+
that such additional attribution notices cannot be construed
|
|
121
|
+
as modifying the License.
|
|
122
|
+
|
|
123
|
+
You may add Your own copyright statement to Your modifications and
|
|
124
|
+
may provide additional or different license terms and conditions
|
|
125
|
+
for use, reproduction, or distribution of Your modifications, or
|
|
126
|
+
for any such Derivative Works as a whole, provided Your use,
|
|
127
|
+
reproduction, and distribution of the Work otherwise complies with
|
|
128
|
+
the conditions stated in this License.
|
|
129
|
+
|
|
130
|
+
5. Submission of Contributions. Unless You explicitly state otherwise,
|
|
131
|
+
any Contribution intentionally submitted for inclusion in the Work
|
|
132
|
+
by You to the Licensor shall be under the terms and conditions of
|
|
133
|
+
this License, without any additional terms or conditions.
|
|
134
|
+
Notwithstanding the above, nothing herein shall supersede or modify
|
|
135
|
+
the terms of any separate license agreement you may have executed
|
|
136
|
+
with Licensor regarding such Contributions.
|
|
137
|
+
|
|
138
|
+
6. Trademarks. This License does not grant permission to use the trade
|
|
139
|
+
names, trademarks, service marks, or product names of the Licensor,
|
|
140
|
+
except as required for reasonable and customary use in describing the
|
|
141
|
+
origin of the Work and reproducing the content of the NOTICE file.
|
|
142
|
+
|
|
143
|
+
7. Disclaimer of Warranty. Unless required by applicable law or
|
|
144
|
+
agreed to in writing, Licensor provides the Work (and each
|
|
145
|
+
Contributor provides its Contributions) on an "AS IS" BASIS,
|
|
146
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
|
|
147
|
+
implied, including, without limitation, any warranties or conditions
|
|
148
|
+
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
|
|
149
|
+
PARTICULAR PURPOSE. You are solely responsible for determining the
|
|
150
|
+
appropriateness of using or redistributing the Work and assume any
|
|
151
|
+
risks associated with Your exercise of permissions under this License.
|
|
152
|
+
|
|
153
|
+
8. Limitation of Liability. In no event and under no legal theory,
|
|
154
|
+
whether in tort (including negligence), contract, or otherwise,
|
|
155
|
+
unless required by applicable law (such as deliberate and grossly
|
|
156
|
+
negligent acts) or agreed to in writing, shall any Contributor be
|
|
157
|
+
liable to You for damages, including any direct, indirect, special,
|
|
158
|
+
incidental, or consequential damages of any character arising as a
|
|
159
|
+
result of this License or out of the use or inability to use the
|
|
160
|
+
Work (including but not limited to damages for loss of goodwill,
|
|
161
|
+
work stoppage, computer failure or malfunction, or any and all
|
|
162
|
+
other commercial damages or losses), even if such Contributor
|
|
163
|
+
has been advised of the possibility of such damages.
|
|
164
|
+
|
|
165
|
+
9. Accepting Warranty or Additional Liability. While redistributing
|
|
166
|
+
the Work or Derivative Works thereof, You may choose to offer,
|
|
167
|
+
and charge a fee for, acceptance of support, warranty, indemnity,
|
|
168
|
+
or other liability obligations and/or rights consistent with this
|
|
169
|
+
License. However, in accepting such obligations, You may act only
|
|
170
|
+
on Your own behalf and on Your sole responsibility, not on behalf
|
|
171
|
+
of any other Contributor, and only if You agree to indemnify,
|
|
172
|
+
defend, and hold each Contributor harmless for any liability
|
|
173
|
+
incurred by, or claims asserted against, such Contributor by reason
|
|
174
|
+
of your accepting any such warranty or additional liability.
|
|
175
|
+
|
|
176
|
+
END OF TERMS AND CONDITIONS
|
|
177
|
+
|
|
178
|
+
APPENDIX: How to apply the Apache License to your work.
|
|
179
|
+
|
|
180
|
+
To apply the Apache License to your work, attach the following
|
|
181
|
+
boilerplate notice, with the fields enclosed by brackets "[]"
|
|
182
|
+
replaced with your own identifying information. (Don't include
|
|
183
|
+
the brackets!) The text should be enclosed in the appropriate
|
|
184
|
+
comment syntax for the file format. We also recommend that a
|
|
185
|
+
file or class name and description of purpose be included on the
|
|
186
|
+
same "printed page" as the copyright notice for easier
|
|
187
|
+
identification within third-party archives.
|
|
188
|
+
|
|
189
|
+
Copyright [yyyy] [name of copyright owner]
|
|
190
|
+
|
|
191
|
+
Licensed under the Apache License, Version 2.0 (the "License");
|
|
192
|
+
you may not use this file except in compliance with the License.
|
|
193
|
+
You may obtain a copy of the License at
|
|
194
|
+
|
|
195
|
+
http://www.apache.org/licenses/LICENSE-2.0
|
|
196
|
+
|
|
197
|
+
Unless required by applicable law or agreed to in writing, software
|
|
198
|
+
distributed under the License is distributed on an "AS IS" BASIS,
|
|
199
|
+
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
|
|
200
|
+
See the License for the specific language governing permissions and
|
|
201
|
+
limitations under the License.
|
package/README.md
CHANGED
|
@@ -1,3 +1,168 @@
|
|
|
1
|
-
#
|
|
1
|
+
# @ezghcloud/flags-openfeature
|
|
2
2
|
|
|
3
|
-
|
|
3
|
+
[OpenFeature](https://openfeature.dev) providers for **EZGH Feature Flags**, in TypeScript:
|
|
4
|
+
|
|
5
|
+
- `@ezghcloud/flags-openfeature/server`: `EzghProvider`, for backends on Node (20+), Bun and Deno.
|
|
6
|
+
It keeps the environment's compiled flags in memory and evaluates locally with flagd's
|
|
7
|
+
open-source core, so an evaluation never makes a network call.
|
|
8
|
+
- `@ezghcloud/flags-openfeature/web`: `EzghWebProvider`, for browsers (React through OpenFeature's
|
|
9
|
+
React SDK). It evaluates remotely, so rules never reach the browser.
|
|
10
|
+
|
|
11
|
+
You write against the OpenFeature API; the provider connects it to EZGH. Licensed Apache-2.0.
|
|
12
|
+
|
|
13
|
+
## Install
|
|
14
|
+
|
|
15
|
+
```bash
|
|
16
|
+
npm install @ezghcloud/flags-openfeature
|
|
17
|
+
bun add @ezghcloud/flags-openfeature
|
|
18
|
+
pnpm add @ezghcloud/flags-openfeature
|
|
19
|
+
```
|
|
20
|
+
|
|
21
|
+
Install the OpenFeature SDK you use alongside it: `@openfeature/server-sdk` for the server
|
|
22
|
+
provider, `@openfeature/web-sdk` (and `@openfeature/react-sdk` for React) for the web provider.
|
|
23
|
+
|
|
24
|
+
## Server provider
|
|
25
|
+
|
|
26
|
+
Create a **server key** (`ezgh_fs_…`) for an environment in the console or with
|
|
27
|
+
`ezgh flags sdk-keys create`, and keep it secret: it can read every flag's rules.
|
|
28
|
+
|
|
29
|
+
```ts
|
|
30
|
+
import { OpenFeature } from "@openfeature/server-sdk"
|
|
31
|
+
import { EzghProvider } from "@ezghcloud/flags-openfeature/server"
|
|
32
|
+
|
|
33
|
+
await OpenFeature.setProviderAndWait(new EzghProvider({ sdkKey: process.env.EZGH_FLAGS_KEY! }))
|
|
34
|
+
const flags = OpenFeature.getClient()
|
|
35
|
+
|
|
36
|
+
if (await flags.getBooleanValue("new-checkout", false, { targetingKey: user.id, plan: user.plan })) {
|
|
37
|
+
// …
|
|
38
|
+
}
|
|
39
|
+
```
|
|
40
|
+
|
|
41
|
+
- **Startup:** the provider fetches the environment's snapshot and is ready once it has it, then
|
|
42
|
+
follows the data plane's sync stream. If the stream fails three times in a row, it polls the
|
|
43
|
+
snapshot every 30 seconds while it keeps retrying the stream (exponential backoff with jitter,
|
|
44
|
+
honouring `Retry-After`).
|
|
45
|
+
- **Changes:** every new snapshot version emits `PROVIDER_CONFIGURATION_CHANGED` with
|
|
46
|
+
`metadata.snapshotVersion` and `flagsChanged`: the flags whose configuration changed, appeared
|
|
47
|
+
or disappeared (a segment edit counts for the flags using it; the list can be empty).
|
|
48
|
+
- **Disconnected** for 30 seconds: it keeps evaluating the last snapshot and emits
|
|
49
|
+
`PROVIDER_STALE`, then `PROVIDER_READY` once it reaches the data plane again.
|
|
50
|
+
- **A revoked or unknown key** is fatal (a stream ending with `revoked` or `environmentDeleted`,
|
|
51
|
+
or a `401`/`403`):
|
|
52
|
+
`PROVIDER_ERROR` with `PROVIDER_FATAL`, the client status becomes `FATAL` (OpenFeature then
|
|
53
|
+
answers defaults), and the provider stops.
|
|
54
|
+
- **Reasons:** `TARGETING_MATCH`, `STATIC`, `DEFAULT`, and `DISABLED` for a flag that's off in
|
|
55
|
+
the environment (with its off value). `flagMetadata.flagVersion` is the flag's config version.
|
|
56
|
+
|
|
57
|
+
### Options
|
|
58
|
+
|
|
59
|
+
| Option | Default | |
|
|
60
|
+
| --- | --- | --- |
|
|
61
|
+
| `sdkKey` | | A server key. Required unless `offline`. |
|
|
62
|
+
| `endpoint` | `https://flags.ezghcloud.com` | The data plane. |
|
|
63
|
+
| `bootstrapPath` | | A snapshot file from `ezgh flags export`. The provider is ready from it without the network, then syncs; the data plane's snapshot replaces it whatever its version. |
|
|
64
|
+
| `offline` | `false` | Use only `bootstrapPath` and never call the network (tests, CI, air-gapped runs). |
|
|
65
|
+
| `timeoutMs` | `10000` | How long `initialize` waits for the first snapshot. On a timeout it fails (status `ERROR`) and keeps trying; it emits `PROVIDER_READY` when the snapshot arrives. |
|
|
66
|
+
| `pollIntervalMs` | `30000` | The snapshot poll interval while the stream is down. |
|
|
67
|
+
| `staleAfterMs` | `30000` | How long without reaching the data plane before `PROVIDER_STALE`. |
|
|
68
|
+
| `minBackoffMs`, `maxBackoffMs` | `1000`, `60000` | Stream reconnect backoff. A `Retry-After` is honoured up to the maximum. A stream ending with `rotate` reconnects at once; `shutdown` after a little jitter; any other reason backs off like a failure. |
|
|
69
|
+
| `idleTimeoutMs` | `45000` | A stream silent this long (the data plane sends a heartbeat every 15 s) is reconnected. |
|
|
70
|
+
| `fetch`, `logger` | global `fetch`, console | |
|
|
71
|
+
|
|
72
|
+
### Offline and tests
|
|
73
|
+
|
|
74
|
+
```ts
|
|
75
|
+
// A file from `ezgh flags export --env production > flags.json`; no network at all.
|
|
76
|
+
await OpenFeature.setProviderAndWait(new EzghProvider({ offline: true, bootstrapPath: "flags.json" }))
|
|
77
|
+
```
|
|
78
|
+
|
|
79
|
+
## Browsers and React
|
|
80
|
+
|
|
81
|
+
Create a **client key** (`ezgh_fc_…`) for the environment. It's publishable: ship it in your
|
|
82
|
+
bundle. A client key only sees flags marked **client-side** (`clientSide: true`); any other flag
|
|
83
|
+
answers `FLAG_NOT_FOUND` exactly as a flag that doesn't exist, and rules never leave EZGH.
|
|
84
|
+
|
|
85
|
+
```ts
|
|
86
|
+
import { OpenFeature } from "@openfeature/web-sdk"
|
|
87
|
+
import { EzghWebProvider } from "@ezghcloud/flags-openfeature/web"
|
|
88
|
+
|
|
89
|
+
await OpenFeature.setContext({ targetingKey: user.id, plan: user.plan })
|
|
90
|
+
OpenFeature.setProvider(new EzghWebProvider({ clientKey: "ezgh_fc_…" }))
|
|
91
|
+
```
|
|
92
|
+
|
|
93
|
+
- **Evaluation:** one bulk evaluation of every client-side flag at startup and on every
|
|
94
|
+
`OpenFeature.setContext`; flags are then answered synchronously from those results.
|
|
95
|
+
- **Refresh:** when the page becomes visible again and every 5 minutes (`refreshMs`), with
|
|
96
|
+
`If-None-Match`, so an unchanged answer costs a `304`. Changes emit
|
|
97
|
+
`PROVIDER_CONFIGURATION_CHANGED` with the flags whose value or variant changed.
|
|
98
|
+
- **Live updates** are opt-in: `new EzghWebProvider({ clientKey, live: true })` keeps one stream
|
|
99
|
+
per tab open and refetches as soon as a client-side flag changes.
|
|
100
|
+
- Nothing is stored in `localStorage` or `sessionStorage`; results live in memory only.
|
|
101
|
+
- A revoked key or a deleted environment is fatal (`PROVIDER_FATAL`), as for the server provider.
|
|
102
|
+
|
|
103
|
+
With React, use OpenFeature's React SDK; there's no EZGH React package:
|
|
104
|
+
|
|
105
|
+
```tsx
|
|
106
|
+
import { OpenFeatureProvider, useBooleanFlagValue } from "@openfeature/react-sdk"
|
|
107
|
+
|
|
108
|
+
function App() {
|
|
109
|
+
return (
|
|
110
|
+
<OpenFeatureProvider>
|
|
111
|
+
<Checkout />
|
|
112
|
+
</OpenFeatureProvider>
|
|
113
|
+
)
|
|
114
|
+
}
|
|
115
|
+
|
|
116
|
+
function Checkout() {
|
|
117
|
+
const newCheckout = useBooleanFlagValue("new-checkout", false)
|
|
118
|
+
return newCheckout ? <NewCheckout /> : <OldCheckout />
|
|
119
|
+
}
|
|
120
|
+
```
|
|
121
|
+
|
|
122
|
+
Options: `clientKey`, `endpoint`, `live` (`false`), `refreshMs` (5 minutes), `timeoutMs` (10 s for
|
|
123
|
+
the first evaluation; it keeps retrying after and emits `PROVIDER_READY`), `minBackoffMs`,
|
|
124
|
+
`maxBackoffMs`, `idleTimeoutMs`, `changedRetryMs` (1 s: after a `changed` whose refetch is a `304`,
|
|
125
|
+
one more refetch this much later), `fetch`, `logger`. A context the data plane refuses (`400
|
|
126
|
+
INVALID_CONTEXT`) isn't retried; the provider answers defaults until the context changes. Each
|
|
127
|
+
live-stream connection refreshes once (conditionally), the first included.
|
|
128
|
+
|
|
129
|
+
## Conformance
|
|
130
|
+
|
|
131
|
+
`test/vectors/` holds flags-stack's conformance vectors (`protocol/vectors/eval`) verbatim, at the
|
|
132
|
+
commit in `.flags-stack-rev`. Every case is evaluated through this package's evaluator and must
|
|
133
|
+
match the value, variant, reason, flag version and error code that flags-stack, the Go provider
|
|
134
|
+
and the Python provider answer. CI checks the copy against flags-stack with a read-only deploy key.
|
|
135
|
+
|
|
136
|
+
To update them: `scripts/sync-vectors.sh ~/code/flags-stack <commit>`, then `bun run check`. Don't
|
|
137
|
+
edit the vectors here; a failing vector is a cross-core disagreement to fix in flags-stack.
|
|
138
|
+
|
|
139
|
+
## Development
|
|
140
|
+
|
|
141
|
+
```bash
|
|
142
|
+
bun install
|
|
143
|
+
bun run check # typecheck, tests (vectors included), build, a Node import smoke test
|
|
144
|
+
```
|
|
145
|
+
|
|
146
|
+
**End to end:** `scripts/e2e.sh <flags-stack checkout>` builds flags-stack and its fake org-api,
|
|
147
|
+
runs `flags-stack all` on `DATABASE_URL` (a database of its own) and `REDIS_URL`, and runs
|
|
148
|
+
`test/e2e/e2e.test.ts`: an environment, a client-side flag and both kinds of key through the API;
|
|
149
|
+
both providers see it off, then on within seconds of a config write; revoking the server key makes
|
|
150
|
+
its provider fatal. CI runs it in the E2E workflow against flags-stack at `.flags-stack-rev`.
|
|
151
|
+
|
|
152
|
+
## Releasing
|
|
153
|
+
|
|
154
|
+
Releases go to npm as `@ezghcloud/flags-openfeature`, published by the Release workflow
|
|
155
|
+
(`.github/workflows/release.yml`) with npm trusted publishing: GitHub Actions OIDC, no npm token,
|
|
156
|
+
provenance attached automatically.
|
|
157
|
+
|
|
158
|
+
1. Bump `version` in `package.json` and commit it on `main`.
|
|
159
|
+
2. Push the tag: `git tag vX.Y.Z && git push origin vX.Y.Z`.
|
|
160
|
+
|
|
161
|
+
On the tag, the workflow checks the tag equals `package.json`'s version, runs `bun run check`,
|
|
162
|
+
builds, packs `dist/`, publishes (skipping a version already on npm) and creates the GitHub
|
|
163
|
+
release. `main` never holds `dist/`.
|
|
164
|
+
|
|
165
|
+
First-time owner setup (once, logged in to npm with 2FA): `scripts/npm-trust.sh
|
|
166
|
+
@ezghcloud/flags-openfeature` publishes a placeholder if the package doesn't exist yet, trusts this
|
|
167
|
+
repository's `release.yml` to publish it, and requires 2FA with tokens disallowed. Keep the
|
|
168
|
+
workflow's filename: the npm trust entry names it.
|
package/dist/server.d.ts
ADDED
|
@@ -0,0 +1,42 @@
|
|
|
1
|
+
import { OpenFeatureEventEmitter, type EvaluationContext, type JsonValue, type Logger, type Provider, type ResolutionDetails } from "@openfeature/server-sdk";
|
|
2
|
+
export { DEFAULT_ENDPOINT } from "./shared/http.ts";
|
|
3
|
+
export interface EzghProviderOptions {
|
|
4
|
+
/** A server SDK key (`ezgh_fs_…`). Required unless `offline`. */
|
|
5
|
+
sdkKey?: string;
|
|
6
|
+
/** The data plane; defaults to https://flags.ezghcloud.com. */
|
|
7
|
+
endpoint?: string;
|
|
8
|
+
/** A snapshot file (`ezgh flags export`): the provider is ready from it without the network. */
|
|
9
|
+
bootstrapPath?: string;
|
|
10
|
+
/** Use only `bootstrapPath`; never call the network (tests, CI, air-gapped runs). */
|
|
11
|
+
offline?: boolean;
|
|
12
|
+
/** The fetch to use; defaults to the global one. */
|
|
13
|
+
fetch?: typeof fetch;
|
|
14
|
+
/** Logs snapshot and connection problems; defaults to console warnings and errors. */
|
|
15
|
+
logger?: Logger;
|
|
16
|
+
/** How long `initialize` waits for the first snapshot (default 10 s). Syncing continues after. */
|
|
17
|
+
timeoutMs?: number;
|
|
18
|
+
/** The snapshot poll interval while the stream is down (default 30 s). */
|
|
19
|
+
pollIntervalMs?: number;
|
|
20
|
+
/** Stale after this long without reaching the data plane (default 30 s). */
|
|
21
|
+
staleAfterMs?: number;
|
|
22
|
+
/** Stream reconnect backoff bounds (default 1 s to 60 s, with jitter). */
|
|
23
|
+
minBackoffMs?: number;
|
|
24
|
+
maxBackoffMs?: number;
|
|
25
|
+
/** A stream that sends nothing (not even a heartbeat) for this long is reconnected (default 45 s). */
|
|
26
|
+
idleTimeoutMs?: number;
|
|
27
|
+
}
|
|
28
|
+
export declare class EzghProvider implements Provider {
|
|
29
|
+
#private;
|
|
30
|
+
readonly metadata: {
|
|
31
|
+
readonly name: "ezgh-flags";
|
|
32
|
+
};
|
|
33
|
+
readonly runsOn: "server";
|
|
34
|
+
readonly events: OpenFeatureEventEmitter;
|
|
35
|
+
constructor(options: EzghProviderOptions);
|
|
36
|
+
initialize(): Promise<void>;
|
|
37
|
+
onClose(): Promise<void>;
|
|
38
|
+
resolveBooleanEvaluation(flagKey: string, defaultValue: boolean, context: EvaluationContext): Promise<ResolutionDetails<boolean>>;
|
|
39
|
+
resolveStringEvaluation(flagKey: string, defaultValue: string, context: EvaluationContext): Promise<ResolutionDetails<string>>;
|
|
40
|
+
resolveNumberEvaluation(flagKey: string, defaultValue: number, context: EvaluationContext): Promise<ResolutionDetails<number>>;
|
|
41
|
+
resolveObjectEvaluation<T extends JsonValue>(flagKey: string, defaultValue: T, context: EvaluationContext): Promise<ResolutionDetails<T>>;
|
|
42
|
+
}
|