Introduce a new push command to the OpenFeature CLI. This command will allow users to push flag configuration changes to upstream remote flag providers. This is the inverse of the existing pull feature (see [PR #147](#147) for context).
Background
There has been considerable discussion on how a push operation should work, including the idea of an extensible plugin system to support multiple flag providers. To get the ball rolling, we’ll start with an opinionated first implementation for a straightforward use case. Once we gain experience from this initial version, it can help inform how to design a future extensible plugin system.
Goals
- Provide a simple
push command that lets users send local flag changes to an upstream remote provider.
- Mirror the structure and UX of the
pull command where possible for familiarity.
- Lay groundwork for eventual extensibility but keep this version intentionally limited to one provider/use case.
Non-Goals
- Building a full plugin system now.
- Supporting multiple providers or complex workflows in the first iteration.
Proposed Approach
- Implement
push as the inverse of pull, using the same core configuration and authentication mechanisms where applicable.
- Start with a single upstream flag provider for a straightforward application.
- Output clear success/error messages when pushing.
- Add basic tests and documentation similar to
pull.
Acceptance Criteria
References
Introduce a new
pushcommand to the OpenFeature CLI. This command will allow users to push flag configuration changes to upstream remote flag providers. This is the inverse of the existingpullfeature (see [PR #147](#147) for context).Background
There has been considerable discussion on how a
pushoperation should work, including the idea of an extensible plugin system to support multiple flag providers. To get the ball rolling, we’ll start with an opinionated first implementation for a straightforward use case. Once we gain experience from this initial version, it can help inform how to design a future extensible plugin system.Goals
pushcommand that lets users send local flag changes to an upstream remote provider.pullcommand where possible for familiarity.Non-Goals
Proposed Approach
pushas the inverse ofpull, using the same core configuration and authentication mechanisms where applicable.pull.Acceptance Criteria
openfeature pushcommand exists and can push flag changes from local configuration to a single remote provider.pullwhere possible.References
pull: [PR #147](feat:openfeature pullcommand #147)