Skip to content

Create Feature

cloudwatchevidently_create_feature R Documentation

Creates an Evidently feature that you want to launch or test

Description

Creates an Evidently feature that you want to launch or test. You can define up to five variations of a feature, and use these variations in your launches and experiments. A feature must be created in a project. For information about creating a project, see create_project.

Don't use this operation to update an existing feature. Instead, use update_feature.

Usage

cloudwatchevidently_create_feature(defaultVariation, description,
  entityOverrides, evaluationStrategy, name, project, tags, variations)

Arguments

defaultVariation

The name of the variation to use as the default variation. The default variation is served to users who are not allocated to any ongoing launches or experiments of this feature.

This variation must also be listed in the variations structure.

If you omit defaultVariation, the first variation listed in the variations structure is used as the default variation.

description

An optional description of the feature.

entityOverrides

Specify users that should always be served a specific variation of a feature. Each user is specified by a key-value pair . For each key, specify a user by entering their user ID, account ID, or some other identifier. For the value, specify the name of the variation that they are to be served.

This parameter is limited to 2500 overrides or a total of 40KB. The 40KB limit includes an overhead of 6 bytes per override.

evaluationStrategy

Specify ALL_RULES to activate the traffic allocation specified by any ongoing launches or experiments. Specify DEFAULT_VARIATION to serve the default variation to all users instead.

name

[required] The name for the new feature.

project

[required] The name or ARN of the project that is to contain the new feature.

tags

Assigns one or more tags (key-value pairs) to the feature.

Tags can help you organize and categorize your resources. You can also use them to scope user permissions by granting a user permission to access or change only resources with certain tag values.

Tags don't have any semantic meaning to Amazon Web Services and are interpreted strictly as strings of characters.

You can associate as many as 50 tags with a feature.

For more information, see Tagging Amazon Web Services resources.

variations

[required] An array of structures that contain the configuration of the feature's different variations.

Value

A list with the following syntax:

list(
  feature = list(
    arn = "string",
    createdTime = as.POSIXct(
      "2015-01-01"
    ),
    defaultVariation = "string",
    description = "string",
    entityOverrides = list(
      "string"
    ),
    evaluationRules = list(
      list(
        name = "string",
        type = "string"
      )
    ),
    evaluationStrategy = "ALL_RULES"|"DEFAULT_VARIATION",
    lastUpdatedTime = as.POSIXct(
      "2015-01-01"
    ),
    name = "string",
    project = "string",
    status = "AVAILABLE"|"UPDATING",
    tags = list(
      "string"
    ),
    valueType = "STRING"|"LONG"|"DOUBLE"|"BOOLEAN",
    variations = list(
      list(
        name = "string",
        value = list(
          boolValue = TRUE|FALSE,
          doubleValue = 123.0,
          longValue = 123,
          stringValue = "string"
        )
      )
    )
  )
)

Request syntax

svc$create_feature(
  defaultVariation = "string",
  description = "string",
  entityOverrides = list(
    "string"
  ),
  evaluationStrategy = "ALL_RULES"|"DEFAULT_VARIATION",
  name = "string",
  project = "string",
  tags = list(
    "string"
  ),
  variations = list(
    list(
      name = "string",
      value = list(
        boolValue = TRUE|FALSE,
        doubleValue = 123.0,
        longValue = 123,
        stringValue = "string"
      )
    )
  )
)