feat(flagd): migrate to new provider mode file and update e2e tests by aepfli · Pull Request #121 · open-feature/python-sdk-contrib · GitHub
Skip to content

feat(flagd): migrate to new provider mode file and update e2e tests - #121

Merged
toddbaert merged 15 commits into
open-feature:mainfrom
open-feature-forking:feat/gherkinmigration
Feb 6, 2025
Merged

toddbaert merged 15 commits into
open-feature:mainfrom
open-feature-forking:feat/gherkinmigration

Conversation

@aepfli

@aepfli aepfli commented Dec 17, 2024 •

Copy link
Copy Markdown
Member

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.

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
aepfli force-pushed the feat/gherkinmigration branch from bd916e4 to 527ce6b Compare December 17, 2024 20:08
@aepfli aepfli changed the title [Draft] improve gherkin setup based on current motivation feat(flagd): improve gherkin setup based on current motivation Dec 18, 2024
@aepfli aepfli changed the title feat(flagd): improve gherkin setup based on current motivation feat(flagd): improve gherkin setup based on current motivation -wip Dec 18, 2024
Signed-off-by: Simon Schrottner <simon.schrottner@dynatrace.com>
@aepfli
aepfli force-pushed the feat/gherkinmigration branch from 527ce6b to 578692f Compare December 18, 2024 06:39
@aepfli aepfli changed the title feat(flagd): improve gherkin setup based on current motivation -wip test(flagd): improve gherkin setup based on current motivation -wip Dec 27, 2024
@codecov

codecov Bot commented Dec 27, 2024 •

Copy link
Copy Markdown

@aepfli
aepfli force-pushed the feat/gherkinmigration branch 4 times, most recently from 35790da to 455d51d Compare December 27, 2024 15:18
Signed-off-by: Simon Schrottner <simon.schrottner@dynatrace.com>
@aepfli
aepfli force-pushed the feat/gherkinmigration branch from 455d51d to 9192c77 Compare December 27, 2024 15:19
Signed-off-by: Simon Schrottner <simon.schrottner@dynatrace.com>
@aepfli
aepfli force-pushed the feat/gherkinmigration branch 6 times, most recently from 55feac0 to 1a8000b Compare January 8, 2025 19:31
@aepfli
aepfli force-pushed the feat/gherkinmigration branch 6 times, most recently from 77961c8 to 1e2803c Compare February 4, 2025 13:56
Comment thread providers/openfeature-provider-flagd/tests/e2e/file/conftest.py Outdated
@aepfli
aepfli force-pushed the feat/gherkinmigration branch from 1e2803c to 6a299b1 Compare February 4, 2025 17:33
@aepfli

aepfli commented Feb 4, 2025

Copy link
Copy Markdown
Member Author

@aepfli
aepfli force-pushed the feat/gherkinmigration branch from 6a299b1 to 1050ca0 Compare February 4, 2025 17:35
Signed-off-by: Simon Schrottner <simon.schrottner@dynatrace.com>
@aepfli
aepfli force-pushed the feat/gherkinmigration branch from 1050ca0 to a5990a3 Compare February 4, 2025 17:36
@toddbaert
toddbaert merged commit eed1ee0 into open-feature:main Feb 6, 2025
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants