open-feature
/
cli
mirror of https://github.com/open-feature/cli.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
OpenFeature’s official command-line tool
47 Commits 20 Branches 18 Tags 732 KiB
Go 67.8%
C# 24%
Shell 4.7%
TypeScript 2.4%
Makefile 0.8%
Other 0.3%
Go to file
OpenFeature Bot e430a8dbe6
chore(main): release 0.1.10 (#65) 
🤖 I have created a release *beep* *boop*
---


##
[0.1.10](https://github.com/open-feature/cli/compare/v0.1.9...v0.1.10)
(2025-01-27)


### ✨ New Features

* add doc gen, move schema path, add tests, fix react gen
([#68](https://github.com/open-feature/cli/issues/68))
([68a72ee](68a72ee929))
* update golang output
([#63](https://github.com/open-feature/cli/issues/63))
([0e7db02](0e7db0209e))


### 🧹 Chore

* go mod tidy, gitignore dist folder
([1530d38](1530d38dd3))
* switch base image from distroless to alpine
([#67](https://github.com/open-feature/cli/issues/67))
([60955af](60955af1a9))

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).

Signed-off-by: OpenFeature Bot <109696520+openfeaturebot@users.noreply.github.com>
 		2025-01-27 15:25:53 +00:00
.github/workflows feat: add doc gen, move schema path, add tests, fix react gen (#68) 2025-01-27 15:20:19 +00:00
cmd feat: add doc gen, move schema path, add tests, fix react gen (#68) 2025-01-27 15:20:19 +00:00
docs feat: add doc gen, move schema path, add tests, fix react gen (#68) 2025-01-27 15:20:19 +00:00
internal feat: add doc gen, move schema path, add tests, fix react gen (#68) 2025-01-27 15:20:19 +00:00
sample
…
schema/v0 feat: add doc gen, move schema path, add tests, fix react gen (#68) 2025-01-27 15:20:19 +00:00
.gitignore chore: go mod tidy, gitignore dist folder 2025-01-01 18:00:49 +00:00
.goreleaser.yaml fix: docker publishing 2024-10-31 15:42:54 -04:00
.release-please-manifest.json chore(main): release 0.1.10 (#65) 2025-01-27 15:25:53 +00:00
CHANGELOG.md chore(main): release 0.1.10 (#65) 2025-01-27 15:25:53 +00:00
Dockerfile chore: switch base image from distroless to alpine (#67) 2025-01-02 14:44:23 -05:00
LICENSE
…
Makefile feat: add doc gen, move schema path, add tests, fix react gen (#68) 2025-01-27 15:20:19 +00:00
README.md docs: switch from code gen to cli (#47) 2024-10-31 19:12:57 +00:00
go.mod feat: add doc gen, move schema path, add tests, fix react gen (#68) 2025-01-27 15:20:19 +00:00
go.sum feat: add doc gen, move schema path, add tests, fix react gen (#68) 2025-01-27 15:20:19 +00:00
main.go refactor: change name of go module (#46) 2024-10-31 19:15:05 +00:00
release-please-config.json ci: update release process (#57) 2024-11-05 15:42:37 -05:00

README.md

OpenFeature Logo

OpenFeature CLI

work-in-progress Slack

[!CAUTION] The OpenFeature CLI is experimental! Feel free to give it a shot and provide feedback, but expect breaking changes.

OpenFeature is an open specification that provides a vendor-agnostic, community-driven API for feature flagging that works with your favorite feature flag management tool or in-house solution.

Overview

The OpenFeature CLI is a command-line tool designed to improve the developer experience when working with feature flags. Currently, features are focused primarily on supporting code generation.

Installation

Download packaged binaries from the releases page.

Why Code Generation?

Code generation automates the creation of strongly typed flag accessors, minimizing configuration errors and providing a better developer experience. By generating these accessors, developers can avoid issues related to incorrect flag names or types, resulting in more reliable and maintainable code.

Goals

  • Unified Flag Manifest Format: Establish a standardized flag manifest format that can be easily converted from existing configurations.
  • Strongly Typed Flag Accessors: Develop a CLI tool to generate strongly typed flag accessors for multiple programming languages.
  • Modular and Extensible Design: Create a format that allows for future extensions and modularization of flags.

Non-Goals

  • Full Provider Integration: The initial scope does not include creating tools to convert provider-specific configurations to the new flag manifest format.
  • Validation of Flag Configs: The project will not initially focus on validating flag configurations for consistency with the flag manifest.
  • General-Purpose Configuration: The project will not aim to create a general-purpose configuration tool for feature flags beyond the scope of the code generation tool.

Support the project

Thanks to everyone who has already contributed

Pictures of the folks who have contributed to the project

Made with contrib.rocks.