# Acceptance Criteria: alibabacloud-cms-dataset

**Scenario**: CMS Dataset Lifecycle Management and Querying
**Purpose**: Skill testing acceptance criteria

---

# Correct CLI Command Patterns

## 1. Product — `cms`

#### CORRECT
```bash
aliyun cms list-datasets --api-version 2024-03-30 ...
```

#### INCORRECT
```bash
aliyun CMS list-datasets ...        # Wrong case
aliyun cloudmonitor list-datasets ... # Wrong product name
```

## 2. API Version — `2024-03-30`

#### CORRECT
```bash
aliyun cms list-datasets --api-version 2024-03-30
```

#### INCORRECT
```bash
aliyun cms list-datasets                          # Missing api-version, defaults to 2019-01-01
aliyun cms list-datasets --api-version 2019-01-01 # Wrong version, dataset APIs not available
```

## 3. Commands — Plugin Mode (kebab-case)

#### CORRECT
```bash
aliyun cms list-datasets ...
aliyun cms get-dataset ...
aliyun cms create-dataset ...
aliyun cms update-dataset ...
aliyun cms delete-dataset ...
aliyun cms execute-query ...
```

#### INCORRECT
```bash
aliyun cms ListDatasets ...    # PascalCase API name, not plugin mode
aliyun cms listDatasets ...    # camelCase, not plugin mode
aliyun cms list_datasets ...   # snake_case, not kebab-case
```

## 4. Parameters — kebab-case naming

#### CORRECT
```bash
--workspace <value>
--dataset-name <value>
--max-results <value>
--next-token <value>
--api-version 2024-03-30
--description <value>
--schema <value>
--type SQL
--query '<value>'
--region cn-hangzhou
```

#### INCORRECT
```bash
--datasetName <value>    # camelCase, not kebab-case
--region-id cn-hangzhou  # Wrong: use --region for CMS dataset commands
--endpoint <value>       # Do not pass --endpoint by default
```

## 5. Schema Format

#### CORRECT — Schema value is the field definitions object
```json
{
  "message_text": {
    "type": "text",
    "chn": true
  },
  "service_name": {
    "type": "text",
    "chn": false
  }
}
```

#### INCORRECT — Schema wraps in API body structure
```json
{
  "datasetName": "app_logs",
  "schema": {
    "message_text": {
      "type": "text"
    }
  }
}
```

## 6. Schema Passing

#### CORRECT
```bash
aliyun cms create-dataset --api-version 2024-03-30 \
  --workspace <workspace> \
  --dataset-name <name> \
  --schema '{"message_text":{"type":"text","chn":true}}'
```

#### INCORRECT
```bash
# Unquoted JSON — shell parsing issues
aliyun cms create-dataset --schema {"field": {"type": "text"}}
```

## 7. Dataset Naming Rules

#### CORRECT
```
app_logs           # 4+ chars, lowercase, starts with letter
service_metric_01  # Digits allowed after first char
trace_id           # Single underscores allowed
```

#### INCORRECT
```
AppLogs      # Uppercase not allowed
app-logs     # Hyphens not allowed
app__logs    # Consecutive underscores not allowed
_app_logs    # Cannot start with underscore
app_logs_    # Cannot end with underscore
app          # Too short (< 4 chars)
```

**Regex**: `^[a-z](?!.*__)[a-z0-9_]{2,61}[a-z0-9]$`

## 8. ExecuteQuery — Type Parameter

#### CORRECT
```bash
aliyun cms execute-query --api-version 2024-03-30 \
  --workspace <workspace> --dataset-name <name> \
  --type SQL --query 'SELECT count(1) FROM "datasetname"'
```

#### INCORRECT
```bash
# Missing --type parameter
aliyun cms execute-query --api-version 2024-03-30 \
  --workspace <workspace> --dataset-name <name> \
  --query 'SELECT count(1) FROM "datasetname"'
```

## 9. Embedding Constraint

#### CORRECT — embedding only on text fields
```json
{
  "message_text": {
    "type": "text",
    "chn": true,
    "embedding": "text-embedding-v4"
  }
}
```

#### INCORRECT — embedding on non-text field
```json
{
  "count_field": {
    "type": "long",
    "embedding": "text-embedding-v4"
  }
}
```

## 10. jsonKeys Nested Structure

#### CORRECT — nested keys with type and chn only
```json
{
  "event_data": {
    "type": "text",
    "chn": false,
    "jsonKeys": {
      "source": {
        "type": "text",
        "chn": false
      },
      "message": {
        "type": "text",
        "chn": true
      }
    }
  }
}
```

#### INCORRECT — embedding inside jsonKeys (not supported)
```json
{
  "event_data": {
    "type": "text",
    "jsonKeys": {
      "source": {
        "type": "text",
        "embedding": "text-embedding-v4"
      }
    }
  }
}
```

## 11. Endpoint Usage

#### CORRECT
```bash
# No endpoint by default — let CLI resolve it
aliyun cms list-datasets --api-version 2024-03-30 --workspace <workspace>

# Only when explicitly required
--endpoint cms.cn-hangzhou.aliyuncs.com
```

#### INCORRECT
```bash
# Wrong endpoint format
--endpoint metrics.cn-hangzhou.aliyuncs.com
```

## 12. Safety — Write Operation Confirmation

#### CORRECT
- Before CreateDataset: check if dataset already exists via ListDatasets
- Before UpdateDataset: show current and new description via GetDataset
- Before DeleteDataset: show dataset details and ask for explicit confirmation

#### INCORRECT
- Creating a dataset without checking for duplicates
- Deleting a dataset without user confirmation
- Updating description without showing the current value

## 13. Product Binding — ONLY use `cms`

#### CORRECT
```bash
aliyun cms list-datasets --api-version 2024-03-30 --workspace <workspace>
aliyun cms create-dataset --api-version 2024-03-30 --workspace <workspace> ...
```

#### INCORRECT — using wrong products
```bash
aliyun dataworks CheckDatasetExistence ...   # Wrong product
aliyun adb DescribeTables ...                # Wrong product
aliyun sls POST /logstores ...               # Wrong product
aliyun maxcompute POST /projects/.../tables  # Wrong product
aliyun opensearch ...                        # Wrong product
```

CMS dataset operations belong to the `cms` product exclusively. The `workspace` parameter is a CMS workspace ID, not a DataWorks workspace, SLS project, or MaxCompute project. If a command fails, fix parameters or permissions — never switch to a different product.

## 14. Credential Handling

#### CORRECT
```bash
aliyun configure list   # Check credential status
```

#### INCORRECT
```bash
echo $ALIBABA_CLOUD_ACCESS_KEY_ID    # NEVER print AK/SK
aliyun configure set --access-key-id LTAI... --access-key-secret 8d...  # NEVER hardcode in agent
```