Flagsmith / Flagsmith/flagsmith-cli

Spike: Support for required metadata

Open
#93 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
12
Forks
3
Avg merge
14h 56m
Merged PRs (30d)
8

Description

In a project with required metadata fields, `flagsmith feature create` always fails:

```
$ flagsmith feature create cli_max_items --value 25 --yes
Error: POST https://api-staging.flagsmith.com/api/v1/projects/6111/features/ returned 400 Bad Request: Missing required metadata field: Required int field
Think this shouldn't happen? Tell us: https://github.com/Flagsmith/flagsmith-cli/issues/new
```

`feature create` has currently no way to send metadata.

We should spot all the commands this affects, and update design documentation with metadata support

Contributor guide

No contributing guide indexed for this repository

Research direction

Start with the `feature create` command and reproduce the required-metadata failure shown in the issue. Inspect the other commands that create or update resources to identify which are affected, then review the existing design documentation. Done means the affected command scope is documented and the metadata-support design is updated.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
cli
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Quiet
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.