{{ message }}
Repository navigation
feat(flagd): migrate to new provider mode file and update e2e tests - #121
Merged
toddbaert merged 15 commits intoFeb 6, 2025
Merged
Conversation
Signed-off-by: Simon Schrottner <simon.schrottner@dynatrace.com>
Signed-off-by: Simon Schrottner <simon.schrottner@dynatrace.com>
Signed-off-by: Simon Schrottner <simon.schrottner@dynatrace.com>
Signed-off-by: Simon Schrottner <simon.schrottner@dynatrace.com>
Signed-off-by: Simon Schrottner <simon.schrottner@dynatrace.com>
Signed-off-by: Simon Schrottner <simon.schrottner@dynatrace.com>
Signed-off-by: Simon Schrottner <simon.schrottner@dynatrace.com>
aepfli
force-pushed
the
feat/gherkinmigration
branch
from
December 17, 2024 20:08
bd916e4 to
527ce6b
Compare
Signed-off-by: Simon Schrottner <simon.schrottner@dynatrace.com>
aepfli
force-pushed
the
feat/gherkinmigration
branch
from
December 18, 2024 06:39
527ce6b to
578692f
Compare
aepfli
force-pushed
the
feat/gherkinmigration
branch
4 times, most recently
from
December 27, 2024 15:18
35790da to
455d51d
Compare
Signed-off-by: Simon Schrottner <simon.schrottner@dynatrace.com>
aepfli
force-pushed
the
feat/gherkinmigration
branch
from
December 27, 2024 15:19
455d51d to
9192c77
Compare
Signed-off-by: Simon Schrottner <simon.schrottner@dynatrace.com>
aepfli
force-pushed
the
feat/gherkinmigration
branch
6 times, most recently
from
January 8, 2025 19:31
55feac0 to
1a8000b
Compare
aepfli
force-pushed
the
feat/gherkinmigration
branch
6 times, most recently
from
February 4, 2025 13:56
77961c8 to
1e2803c
Compare
beeme1mr
approved these changes
Feb 4, 2025
aepfli
force-pushed
the
feat/gherkinmigration
branch
from
February 4, 2025 17:33
1e2803c to
6a299b1
Compare
Member
Author
aepfli
force-pushed
the
feat/gherkinmigration
branch
from
February 4, 2025 17:35
6a299b1 to
1050ca0
Compare
Signed-off-by: Simon Schrottner <simon.schrottner@dynatrace.com>
aepfli
force-pushed
the
feat/gherkinmigration
branch
from
February 4, 2025 17:36
1050ca0 to
a5990a3
Compare
aepfli
added a commit
that referenced
this pull request
Sep 13, 2026
`FlagdContainer` creates `./flags` relative to the package directory and points the launchpad's FLAGS_DIR at it, so every e2e run leaves a 27KB `providers/openfeature-provider-flagd/flags/allFlags.json` behind. The directory is tracked through a `.gitkeep` and no ignore rule matches the file, so the working tree is dirty after any run and a `git add -A` commits a generated fixture. The rule is the one this package already wrote for the same file in the other flag directory: `tests/flags/.gitignore` has contained exactly `allFlags.json` since #121. This is that line, next to the directory that now receives it. Unrelated to the conformance suite, which drives its stack through Compose and writes nothing here -- it is in this branch because this is the branch that touches this package, and it reverts on its own. Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
aepfli
added a commit
that referenced
this pull request
Sep 13, 2026
`FlagdContainer` creates `./flags` relative to the package directory and points the launchpad's FLAGS_DIR at it, so every e2e run leaves a 27KB `providers/openfeature-provider-flagd/flags/allFlags.json` behind. The directory is tracked through a `.gitkeep` and no ignore rule matches the file, so the working tree is dirty after any run and a `git add -A` commits a generated fixture. The rule is the one this package already wrote for the same file in the other flag directory: `tests/flags/.gitignore` has contained exactly `allFlags.json` since #121. This is that line, next to the directory that now receives it. Unrelated to the conformance suite, which drives its stack through Compose and writes nothing here -- it is in this branch because this is the branch that touches this package, and it reverts on its own. Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
aepfli
added a commit
that referenced
this pull request
Sep 13, 2026
`FlagdContainer` creates `./flags` relative to the package directory and points the launchpad's FLAGS_DIR at it, so every e2e run leaves a 27KB `providers/openfeature-provider-flagd/flags/allFlags.json` behind. The directory is tracked through a `.gitkeep` and no ignore rule matches the file, so the working tree is dirty after any run and a `git add -A` commits a generated fixture. The rule is the one this package already wrote for the same file in the other flag directory: `tests/flags/.gitignore` has contained exactly `allFlags.json` since #121. This is that line, next to the directory that now receives it. Unrelated to the conformance suite, which drives its stack through Compose and writes nothing here -- it is in this branch because this is the branch that touches this package, and it reverts on its own. Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
aepfli
added a commit
that referenced
this pull request
Sep 14, 2026
`FlagdContainer` creates `./flags` relative to the package directory and points the launchpad's FLAGS_DIR at it, so every e2e run leaves a 27KB `providers/openfeature-provider-flagd/flags/allFlags.json` behind. The directory is tracked through a `.gitkeep` and no ignore rule matches the file, so the working tree is dirty after any run and a `git add -A` commits a generated fixture. The rule is the one this package already wrote for the same file in the other flag directory: `tests/flags/.gitignore` has contained exactly `allFlags.json` since #121. This is that line, next to the directory that now receives it. Unrelated to the conformance suite, which drives its stack through Compose and writes nothing here -- it is in this branch because this is the branch that touches this package, and it reverts on its own. Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
aepfli
added a commit
that referenced
this pull request
Sep 15, 2026
`FlagdContainer` creates `./flags` relative to the package directory and points the launchpad's FLAGS_DIR at it, so every e2e run leaves a 27KB `providers/openfeature-provider-flagd/flags/allFlags.json` behind. The directory is tracked through a `.gitkeep` and no ignore rule matches the file, so the working tree is dirty after any run and a `git add -A` commits a generated fixture. The rule is the one this package already wrote for the same file in the other flag directory: `tests/flags/.gitignore` has contained exactly `allFlags.json` since #121. This is that line, next to the directory that now receives it. Unrelated to the conformance suite, which drives its stack through Compose and writes nothing here -- it is in this branch because this is the branch that touches this package, and it reverts on its own. Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
aepfli
added a commit
that referenced
this pull request
Sep 16, 2026
`FlagdContainer` creates `./flags` relative to the package directory and points the launchpad's FLAGS_DIR at it, so every e2e run leaves a 27KB `providers/openfeature-provider-flagd/flags/allFlags.json` behind. The directory is tracked through a `.gitkeep` and no ignore rule matches the file, so the working tree is dirty after any run and a `git add -A` commits a generated fixture. The rule is the one this package already wrote for the same file in the other flag directory: `tests/flags/.gitignore` has contained exactly `allFlags.json` since #121. This is that line, next to the directory that now receives it. Unrelated to the conformance suite, which drives its stack through Compose and writes nothing here -- it is in this branch because this is the branch that touches this package, and it reverts on its own. Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
aepfli
added a commit
that referenced
this pull request
Sep 16, 2026
`FlagdContainer` creates `./flags` relative to the package directory and points the launchpad's FLAGS_DIR at it, so every e2e run leaves a 27KB `providers/openfeature-provider-flagd/flags/allFlags.json` behind. The directory is tracked through a `.gitkeep` and no ignore rule matches the file, so the working tree is dirty after any run and a `git add -A` commits a generated fixture. The rule is the one this package already wrote for the same file in the other flag directory: `tests/flags/.gitignore` has contained exactly `allFlags.json` since #121. This is that line, next to the directory that now receives it. Unrelated to the conformance suite, which drives its stack through Compose and writes nothing here -- it is in this branch because this is the branch that touches this package, and it reverts on its own. Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
aepfli
added a commit
that referenced
this pull request
Oct 1, 2026
`FlagdContainer` creates `./flags` relative to the package directory and points the launchpad's FLAGS_DIR at it, so every e2e run leaves a 27KB `providers/openfeature-provider-flagd/flags/allFlags.json` behind. The directory is tracked through a `.gitkeep` and no ignore rule matches the file, so the working tree is dirty after any run and a `git add -A` commits a generated fixture. The rule is the one this package already wrote for the same file in the other flag directory: `tests/flags/.gitignore` has contained exactly `allFlags.json` since #121. This is that line, next to the directory that now receives it. Unrelated to the conformance suite, which drives its stack through Compose and writes nothing here -- it is in this branch because this is the branch that touches this package, and it reverts on its own. Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
aepfli
added a commit
that referenced
this pull request
Oct 2, 2026
`FlagdContainer` creates `./flags` relative to the package directory and points the launchpad's FLAGS_DIR at it, so every e2e run leaves a 27KB `providers/openfeature-provider-flagd/flags/allFlags.json` behind. The directory is tracked through a `.gitkeep` and no ignore rule matches the file, so the working tree is dirty after any run and a `git add -A` commits a generated fixture. The rule is the one this package already wrote for the same file in the other flag directory: `tests/flags/.gitignore` has contained exactly `allFlags.json` since #121. This is that line, next to the directory that now receives it. Unrelated to the conformance suite, which drives its stack through Compose and writes nothing here -- it is in this branch because this is the branch that touches this package, and it reverts on its own. Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
aepfli
added a commit
that referenced
this pull request
Oct 8, 2026
`FlagdContainer` creates `./flags` relative to the package directory and points the launchpad's FLAGS_DIR at it, so every e2e run leaves a 27KB `providers/openfeature-provider-flagd/flags/allFlags.json` behind. The directory is tracked through a `.gitkeep` and no ignore rule matches the file, so the working tree is dirty after any run and a `git add -A` commits a generated fixture. The rule is the one this package already wrote for the same file in the other flag directory: `tests/flags/.gitignore` has contained exactly `allFlags.json` since #121. This is that line, next to the directory that now receives it. Unrelated to the conformance suite, which drives its stack through Compose and writes nothing here -- it is in this branch because this is the branch that touches this package, and it reverts on its own. Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
aepfli
added a commit
that referenced
this pull request
Oct 9, 2026
`FlagdContainer` creates `./flags` relative to the package directory and points the launchpad's FLAGS_DIR at it, so every e2e run leaves a 27KB `providers/openfeature-provider-flagd/flags/allFlags.json` behind. The directory is tracked through a `.gitkeep` and no ignore rule matches the file, so the working tree is dirty after any run and a `git add -A` commits a generated fixture. The rule is the one this package already wrote for the same file in the other flag directory: `tests/flags/.gitignore` has contained exactly `allFlags.json` since #121. This is that line, next to the directory that now receives it. Unrelated to the conformance suite, which drives its stack through Compose and writes nothing here -- it is in this branch because this is the branch that touches this package, and it reverts on its own. Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
aepfli
added a commit
that referenced
this pull request
Oct 14, 2026
`FlagdContainer` creates `./flags` relative to the package directory and points the launchpad's FLAGS_DIR at it, so every e2e run leaves a 27KB `providers/openfeature-provider-flagd/flags/allFlags.json` behind. The directory is tracked through a `.gitkeep` and no ignore rule matches the file, so the working tree is dirty after any run and a `git add -A` commits a generated fixture. The rule is the one this package already wrote for the same file in the other flag directory: `tests/flags/.gitignore` has contained exactly `allFlags.json` since #121. This is that line, next to the directory that now receives it. Unrelated to the conformance suite, which drives its stack through Compose and writes nothing here -- it is in this branch because this is the branch that touches this package, and it reverts on its own. Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
aepfli
added a commit
that referenced
this pull request
Oct 14, 2026
`FlagdContainer` creates `./flags` relative to the package directory and points the launchpad's FLAGS_DIR at it, so every e2e run leaves a 27KB `providers/openfeature-provider-flagd/flags/allFlags.json` behind. The directory is tracked through a `.gitkeep` and no ignore rule matches the file, so the working tree is dirty after any run and a `git add -A` commits a generated fixture. The rule is the one this package already wrote for the same file in the other flag directory: `tests/flags/.gitignore` has contained exactly `allFlags.json` since #121. This is that line, next to the directory that now receives it. Unrelated to the conformance suite, which drives its stack through Compose and writes nothing here -- it is in this branch because this is the branch that touches this package, and it reverts on its own. Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
aepfli
added a commit
that referenced
this pull request
Oct 16, 2026
`FlagdContainer` creates `./flags` relative to the package directory and points the launchpad's FLAGS_DIR at it, so every e2e run leaves a 27KB `providers/openfeature-provider-flagd/flags/allFlags.json` behind. The directory is tracked through a `.gitkeep` and no ignore rule matches the file, so the working tree is dirty after any run and a `git add -A` commits a generated fixture. The rule is the one this package already wrote for the same file in the other flag directory: `tests/flags/.gitignore` has contained exactly `allFlags.json` since #121. This is that line, next to the directory that now receives it. Unrelated to the conformance suite, which drives its stack through Compose and writes nothing here -- it is in this branch because this is the branch that touches this package, and it reverts on its own. Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
aepfli
added a commit
that referenced
this pull request
Oct 16, 2026
`FlagdContainer` creates `./flags` relative to the package directory and points the launchpad's FLAGS_DIR at it, so every e2e run leaves a 27KB `providers/openfeature-provider-flagd/flags/allFlags.json` behind. The directory is tracked through a `.gitkeep` and no ignore rule matches the file, so the working tree is dirty after any run and a `git add -A` commits a generated fixture. The rule is the one this package already wrote for the same file in the other flag directory: `tests/flags/.gitignore` has contained exactly `allFlags.json` since #121. This is that line, next to the directory that now receives it. Unrelated to the conformance suite, which drives its stack through Compose and writes nothing here -- it is in this branch because this is the branch that touches this package, and it reverts on its own. Signed-off-by: Simon Schrottner <simon.schrottner@flagsmith.com>
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
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.

see open-feature/flagd#1504
this pr migrates the offline file provider in a backwards-compatible manner to its own provider.
Furthermore, we're updating the test harness to the new testbed approach.