Creates a new flag. Flags are used to control part of an application by defining a set of rules that deterministically or randomly assign variants to users.
Only the flag_id is required when creating the flag, the remaining
attributes can be set by calling UpdateFlag. When creating a flag it will
start in the ACTIVE state, when you no longer need a flag you can call
ArchiveFlag.
Bearer authentication header of the form Bearer <token>, where <token> is your auth token.
The ID to use for the flag, which will become the final component of the flag's resource name.
This value should be 4-63 characters, and valid characters are /[a-z][0-9]-/.
The body is of type object.
OK
A flag controlling how entities are assigned variants.
The display name of the flag.
For example:
my-flag
The current state of the flag.
Time when the flag was first created.
Time when the flag was last updated.
Reference to the identity that created this flag.
Reference to the identity that last updated this flag.
The resource name of the flag.
For example:
flags/my-flag
A description for the flag.
Schema for the value of each variant.
List of variants for this flag. When a client resolves this flag, it will be assigned exactly one of the variants in this list along with its value.
List of ordered rules that determines how entities are assigned to variants. When a client resolves this flag, each rule will be tried in order, the first rule that match, will provide a variant assignment. If not rule matches, no variant will be assigned.
List of clients that this flag is enabled for.
Time when the flag was archived.
General labels for this flag.
Semi-realtime usage statistics for the flag.
The owner of the resource. If not set will default to the creator.