huaweicloud-devkit 1.0.2-dev.9 → 1.0.2-next.0

package/plugins/huaweicloud-core/skills/huawei-functiongraph/references/deploy-workflow.md

@@ -1,119 +1,119 @@
-# End-to-End Deployment Workflow
-
-```
-1. Write code     → Create index.py with handler function
-2. Package        → zip -j function.zip index.py (no directory nesting!)
-3. Create function → hcloud FunctionGraph CreateFunction (inline for small demos, zip for production)
-4. Verify         → hcloud FunctionGraph InvokeFunction
-5. Create trigger  → hcloud FunctionGraph CreateFunctionTrigger (TIMER for testing, DEDICATEDGATEWAY for HTTP)
-```
-
-## Quick Demo (Inline — No File Packaging)
-
-Use inline for small demo functions (<10KB):
-
-```bash
-# 1. Prepare base64-encoded code
-python3 -c "
-import base64
-code = '''import json
-def handler(event, context):
-    return {'statusCode': 200, 'body': json.dumps({'message': 'Hello FunctionGraph!'}), 'headers': {'Content-Type': 'application/json'}}
-'''
-print(base64.b64encode(code.encode()).decode())
-"
-
-# 2. Create function with inline code (paste base64 output as --func_code.file)
-hcloud FunctionGraph CreateFunction --help
-hcloud FunctionGraph CreateFunction \
-  --func_name=my-backend \
-  --runtime=Python3.10 \
-  --handler=index.handler \
-  --memory_size=256 \
-  --package=default \
-  --timeout=30 \
-  --code_type=inline \
-  --func_code.file=<base64-from-step-1> \
-  --cli-region=<region> \
-  --project_id=<project-id>
-
-# 3. Verify
-hcloud FunctionGraph InvokeFunction \
-  --function_urn=<urn> \
-  --name=test-event \
-  --x_cff_request_version=v0
-```
-
-## Production Deployment (Zip)
-
-```bash
-# 1. Write code
-cat > index.py << 'EOF'
-import json
-
-def handler(event, context):
-    return {
-        "statusCode": 200,
-        "body": json.dumps({"message": "Hello from FunctionGraph!"}),
-        "headers": {"Content-Type": "application/json"}
-    }
-EOF
-
-# 2. Package — CRITICAL: use -j to flatten, no directory nesting
-zip -j function.zip index.py
-
-# 3. Create function (discover params with --help first!)
-hcloud FunctionGraph CreateFunction --help
-# Required: --func_name, --runtime, --handler, --memory_size, --package, --timeout
-# Code type: use --code_type=zip --code_filename=function.zip
-# IMPORTANT: cd to function.zip directory first! --code_filename is filename only.
-
-# 4. Verify (store URN from step 3 output)
-hcloud FunctionGraph InvokeFunction --help
-# Requires body param: --name=test-event (becomes event body passed to handler)
-hcloud FunctionGraph InvokeFunction \
-  --function_urn=<urn> \
-  --name=test-event \
-  --x_cff_request_version=v0
-
-# 5. Create trigger (see references/triggers.md)
-# For quick testing: TIMER trigger (no prerequisites)
-# For HTTP access: DEDICATEDGATEWAY (requires APIG instance — see pre-flight checklist below)
-
-# 5a. TIMER (simple — no APIG dependency)
-hcloud FunctionGraph CreateFunctionTrigger \
-  --function_urn=<urn> \
-  --trigger_type_code=TIMER \
-  --event_type_code=MessageCreated \
-  --trigger_status=ACTIVE \
-  --event_data.name=test-timer \
-  --event_data.schedule_type=Rate \
-  --event_data.schedule="5m"
-```
-
-## DEDICATEDGATEWAY Pre-Flight Checklist
-
-Before creating a DEDICATEDGATEWAY (HTTP) trigger, verify these prerequisites exist:
-
-```bash
-# 1. Check for APIG dedicated instance
-hcloud APIG ListInstancesV2 --cli-region=<r>
-
-# 2. If no instance exists, create one (see huawei-apig skill)
-#    Key: --spec_id=PROFESSIONAL --loadbalancer_provider=elb for public access
-#    Requires: VPC, subnet, security group, enterprise_project_id
-
-# 3. Once instance is Running with public IP, create API group
-hcloud APIG CreateApiGroupV2 --instance_id=<id> --name=<group-name>
-
-# 4. Create DEDICATEDGATEWAY trigger (see references/triggers.md)
-
-# 5. Publish the API (after trigger creation)
-hcloud APIG BatchPublishOrOfflineApiV2 \
-  --instance_id=<apig-instance-id> \
-  --action=online \
-  --env_id=<env-id> \
-  --api_ids=<api-id-from-trigger-response>
-```
-
-If no APIG instance is available, use TIMER trigger for function testing instead.
+# End-to-End Deployment Workflow
+
+```
+1. Write code     → Create index.py with handler function
+2. Package        → zip -j function.zip index.py (no directory nesting!)
+3. Create function → hcloud FunctionGraph CreateFunction (inline for small demos, zip for production)
+4. Verify         → hcloud FunctionGraph InvokeFunction
+5. Create trigger  → hcloud FunctionGraph CreateFunctionTrigger (TIMER for testing, DEDICATEDGATEWAY for HTTP)
+```
+
+## Quick Demo (Inline — No File Packaging)
+
+Use inline for small demo functions (<10KB):
+
+```bash
+# 1. Prepare base64-encoded code
+python3 -c "
+import base64
+code = '''import json
+def handler(event, context):
+    return {'statusCode': 200, 'body': json.dumps({'message': 'Hello FunctionGraph!'}), 'headers': {'Content-Type': 'application/json'}}
+'''
+print(base64.b64encode(code.encode()).decode())
+"
+
+# 2. Create function with inline code (paste base64 output as --func_code.file)
+hcloud FunctionGraph CreateFunction --help
+hcloud FunctionGraph CreateFunction \
+  --func_name=my-backend \
+  --runtime=Python3.10 \
+  --handler=index.handler \
+  --memory_size=256 \
+  --package=default \
+  --timeout=30 \
+  --code_type=inline \
+  --func_code.file=<base64-from-step-1> \
+  --cli-region=<region> \
+  --project_id=<project-id>
+
+# 3. Verify
+hcloud FunctionGraph InvokeFunction \
+  --function_urn=<urn> \
+  --name=test-event \
+  --x_cff_request_version=v0
+```
+
+## Production Deployment (Zip)
+
+```bash
+# 1. Write code
+cat > index.py << 'EOF'
+import json
+
+def handler(event, context):
+    return {
+        "statusCode": 200,
+        "body": json.dumps({"message": "Hello from FunctionGraph!"}),
+        "headers": {"Content-Type": "application/json"}
+    }
+EOF
+
+# 2. Package — CRITICAL: use -j to flatten, no directory nesting
+zip -j function.zip index.py
+
+# 3. Create function (discover params with --help first!)
+hcloud FunctionGraph CreateFunction --help
+# Required: --func_name, --runtime, --handler, --memory_size, --package, --timeout
+# Code type: use --code_type=zip --code_filename=function.zip
+# IMPORTANT: cd to function.zip directory first! --code_filename is filename only.
+
+# 4. Verify (store URN from step 3 output)
+hcloud FunctionGraph InvokeFunction --help
+# Requires body param: --name=test-event (becomes event body passed to handler)
+hcloud FunctionGraph InvokeFunction \
+  --function_urn=<urn> \
+  --name=test-event \
+  --x_cff_request_version=v0
+
+# 5. Create trigger (see references/triggers.md)
+# For quick testing: TIMER trigger (no prerequisites)
+# For HTTP access: DEDICATEDGATEWAY (requires APIG instance — see pre-flight checklist below)
+
+# 5a. TIMER (simple — no APIG dependency)
+hcloud FunctionGraph CreateFunctionTrigger \
+  --function_urn=<urn> \
+  --trigger_type_code=TIMER \
+  --event_type_code=MessageCreated \
+  --trigger_status=ACTIVE \
+  --event_data.name=test-timer \
+  --event_data.schedule_type=Rate \
+  --event_data.schedule="5m"
+```
+
+## DEDICATEDGATEWAY Pre-Flight Checklist
+
+Before creating a DEDICATEDGATEWAY (HTTP) trigger, verify these prerequisites exist:
+
+```bash
+# 1. Check for APIG dedicated instance
+hcloud APIG ListInstancesV2 --cli-region=<r>
+
+# 2. If no instance exists, create one (see huawei-apig skill)
+#    Key: --spec_id=PROFESSIONAL --loadbalancer_provider=elb for public access
+#    Requires: VPC, subnet, security group, enterprise_project_id
+
+# 3. Once instance is Running with public IP, create API group
+hcloud APIG CreateApiGroupV2 --instance_id=<id> --name=<group-name>
+
+# 4. Create DEDICATEDGATEWAY trigger (see references/triggers.md)
+
+# 5. Publish the API (after trigger creation)
+hcloud APIG BatchPublishOrOfflineApiV2 \
+  --instance_id=<apig-instance-id> \
+  --action=online \
+  --env_id=<env-id> \
+  --api_ids=<api-id-from-trigger-response>
+```
+
+If no APIG instance is available, use TIMER trigger for function testing instead.

package/plugins/huaweicloud-core/skills/huawei-functiongraph/references/triggers.md

@@ -1,142 +1,142 @@
-# Triggers
-
-**Always run `hcloud FunctionGraph CreateFunctionTrigger --help` first** for exact parameter names and requirements.
-
-## KooCLI event_data Format (CRITICAL)
-
-KooCLI uses **dotted key-value format**, NOT JSON strings:
-
-```bash
-# CORRECT
---event_data.name=my-api --event_data.auth=IAM --event_data.path=/test
-
-# WRONG — will fail
---event_data='{"name":"my-api","auth":"IAM","path":"/test"}'
-```
-
-## Trigger Types
-
-| Type | `--trigger_type_code` | Notes |
-|------|----------------------|-------|
-| APIG Dedicated | `DEDICATEDGATEWAY` | Use this, not `APIG` (deprecated). Requires APIG instance. |
-| Timer / Cron | `TIMER` | Simplest trigger for testing. No APIG dependency. |
-| OBS | `OBS` | Event when objects created/deleted in bucket |
-| SMN | `SMN` | Message notification trigger |
-
-## TIMER Trigger (Simple Testing)
-
-The TIMER trigger is the easiest path for verifying a function works — no APIG instance needed:
-
-```bash
-hcloud FunctionGraph CreateFunctionTrigger \
-  --function_urn=<urn> \
-  --trigger_type_code=TIMER \
-  --event_type_code=MessageCreated \
-  --trigger_status=ACTIVE \
-  --event_data.name=<trigger-name> \
-  --event_data.schedule_type=Rate \
-  --event_data.schedule="1m"
-```
-
-## DEDICATEDGATEWAY Trigger (HTTP Access)
-
-`trigger_type_code=APIG` is **deprecated**. Use `DEDICATEDGATEWAY` for KooCLI 7.x.
-
-### Required Parameters (Hidden Optional)
-
-These are labeled optional by `--help` but are **required** for DEDICATEDGATEWAY:
-
-| Param | Note |
-|-------|------|
-| `--event_data.protocol` | `HTTPS` or `HTTP` or `BOTH` |
-| `--event_data.sl_domain` | Subdomain from APIG instance (e.g. `xxxx.apic.<region>.huaweicloudapis.com`) |
-| `--event_data.env_name` | API environment name (`RELEASE`) |
-| `--event_data.env_id` | API environment ID |
-| `--event_data.instance_id` | APIG dedicated instance ID |
-| `--event_data.group_id` | API group ID |
-| `--event_data.name` | API name — **hyphens (`-`) are DISALLOWED**. Use underscores (`_`) instead. |
-
-### Error Mapping
-
-| Error | Root Cause → Fix |
-|-------|-----------------|
-| FSS.1417 | Missing `instance_id`, `group_id`, `protocol`, `env_name`, or `env_id`. These are labeled optional but REQUIRED. |
-| API name regex fail | Rename API — remove hyphens (`-`), use `[a-zA-Z0-9_]+` only. |
-
-### Example
-
-```bash
-hcloud FunctionGraph CreateFunctionTrigger \
-  --function_urn=<urn> \
-  --trigger_type_code=DEDICATEDGATEWAY \
-  --event_type_code=APICreated \
-  --trigger_status=ACTIVE \
-  --event_data.name=<api-name-no-hyphens> \
-  --event_data.auth=IAM \
-  --event_data.path=/my-backend \
-  --event_data.match_mode=SWA \
-  --event_data.type=1 \
-  --event_data.protocol=HTTPS \
-  --event_data.req_method=ANY \
-  --event_data.func_info.timeout=5000 \
-  --event_data.instance_id=<apig-instance-id> \
-  --event_data.group_id=<api-group-id> \
-  --event_data.sl_domain=<sl-domain> \
-  --event_data.env_name=RELEASE \
-  --event_data.env_id=<env-id>
-```
-
-After trigger creation, you must **publish** the API before it's accessible:
-
-```bash
-hcloud APIG BatchPublishOrOfflineApiV2 \
-  --instance_id=<apig-instance-id> \
-  --action=online \
-  --env_id=<env-id> \
-  --api_ids=<api-id-from-trigger-response>
-```
-
-### Alternative: --cli-jsonInput (Recommended for Complex Configs)
-
-For trigger configs with many nested fields, use `--cli-jsonInput` to avoid shell escaping issues:
-
-```bash
-cat > trigger.json << 'EOF'
-{
-  "trigger_type_code": "DEDICATEDGATEWAY",
-  "trigger_status": "ACTIVE",
-  "event_type_code": "APICreated",
-  "event_data": {
-    "name": "my-api",
-    "auth": "IAM",
-    "path": "/my-backend",
-    "match_mode": "SWA",
-    "type": 1,
-    "protocol": "HTTPS",
-    "req_method": "ANY",
-    "func_info": { "timeout": 5000 },
-    "instance_id": "<apig-instance-id>",
-    "group_id": "<api-group-id>",
-    "sl_domain": "<sl-domain>",
-    "env_name": "RELEASE",
-    "env_id": "<env-id>"
-  }
-}
-EOF
-hcloud FunctionGraph CreateFunctionTrigger \
-  --function_urn=<urn> \
-  --cli-region=<region> \
-  --project_id=<project_id> \
-  --cli-jsonInput=trigger.json
-```
-
-## List / Delete Triggers
-
-```bash
-hcloud FunctionGraph ListFunctionTriggers --function_urn=<urn>
-hcloud FunctionGraph DeleteFunctionTrigger --function_urn=<urn> --trigger_type_code=<type> --trigger_id=<id>
-```
-
-> Deleting a trigger does NOT cascade-delete the associated APIG API. After `DeleteFunctionTrigger`, also run `hcloud APIG ListApisV2 --instance_id=<id>` and delete orphaned APIs to avoid resource residue.
->
-> **APIG event format**: When using DEDICATEDGATEWAY, the event body is Base64 encoded and uses a non-standard structure. See `apig-event-format.md` for handler templates.
+# Triggers
+
+**Always run `hcloud FunctionGraph CreateFunctionTrigger --help` first** for exact parameter names and requirements.
+
+## KooCLI event_data Format (CRITICAL)
+
+KooCLI uses **dotted key-value format**, NOT JSON strings:
+
+```bash
+# CORRECT
+--event_data.name=my-api --event_data.auth=IAM --event_data.path=/test
+
+# WRONG — will fail
+--event_data='{"name":"my-api","auth":"IAM","path":"/test"}'
+```
+
+## Trigger Types
+
+| Type | `--trigger_type_code` | Notes |
+|------|----------------------|-------|
+| APIG Dedicated | `DEDICATEDGATEWAY` | Use this, not `APIG` (deprecated). Requires APIG instance. |
+| Timer / Cron | `TIMER` | Simplest trigger for testing. No APIG dependency. |
+| OBS | `OBS` | Event when objects created/deleted in bucket |
+| SMN | `SMN` | Message notification trigger |
+
+## TIMER Trigger (Simple Testing)
+
+The TIMER trigger is the easiest path for verifying a function works — no APIG instance needed:
+
+```bash
+hcloud FunctionGraph CreateFunctionTrigger \
+  --function_urn=<urn> \
+  --trigger_type_code=TIMER \
+  --event_type_code=MessageCreated \
+  --trigger_status=ACTIVE \
+  --event_data.name=<trigger-name> \
+  --event_data.schedule_type=Rate \
+  --event_data.schedule="1m"
+```
+
+## DEDICATEDGATEWAY Trigger (HTTP Access)
+
+`trigger_type_code=APIG` is **deprecated**. Use `DEDICATEDGATEWAY` for KooCLI 7.x.
+
+### Required Parameters (Hidden Optional)
+
+These are labeled optional by `--help` but are **required** for DEDICATEDGATEWAY:
+
+| Param | Note |
+|-------|------|
+| `--event_data.protocol` | `HTTPS` or `HTTP` or `BOTH` |
+| `--event_data.sl_domain` | Subdomain from APIG instance (e.g. `xxxx.apic.<region>.huaweicloudapis.com`) |
+| `--event_data.env_name` | API environment name (`RELEASE`) |
+| `--event_data.env_id` | API environment ID |
+| `--event_data.instance_id` | APIG dedicated instance ID |
+| `--event_data.group_id` | API group ID |
+| `--event_data.name` | API name — **hyphens (`-`) are DISALLOWED**. Use underscores (`_`) instead. |
+
+### Error Mapping
+
+| Error | Root Cause → Fix |
+|-------|-----------------|
+| FSS.1417 | Missing `instance_id`, `group_id`, `protocol`, `env_name`, or `env_id`. These are labeled optional but REQUIRED. |
+| API name regex fail | Rename API — remove hyphens (`-`), use `[a-zA-Z0-9_]+` only. |
+
+### Example
+
+```bash
+hcloud FunctionGraph CreateFunctionTrigger \
+  --function_urn=<urn> \
+  --trigger_type_code=DEDICATEDGATEWAY \
+  --event_type_code=APICreated \
+  --trigger_status=ACTIVE \
+  --event_data.name=<api-name-no-hyphens> \
+  --event_data.auth=IAM \
+  --event_data.path=/my-backend \
+  --event_data.match_mode=SWA \
+  --event_data.type=1 \
+  --event_data.protocol=HTTPS \
+  --event_data.req_method=ANY \
+  --event_data.func_info.timeout=5000 \
+  --event_data.instance_id=<apig-instance-id> \
+  --event_data.group_id=<api-group-id> \
+  --event_data.sl_domain=<sl-domain> \
+  --event_data.env_name=RELEASE \
+  --event_data.env_id=<env-id>
+```
+
+After trigger creation, you must **publish** the API before it's accessible:
+
+```bash
+hcloud APIG BatchPublishOrOfflineApiV2 \
+  --instance_id=<apig-instance-id> \
+  --action=online \
+  --env_id=<env-id> \
+  --api_ids=<api-id-from-trigger-response>
+```
+
+### Alternative: --cli-jsonInput (Recommended for Complex Configs)
+
+For trigger configs with many nested fields, use `--cli-jsonInput` to avoid shell escaping issues:
+
+```bash
+cat > trigger.json << 'EOF'
+{
+  "trigger_type_code": "DEDICATEDGATEWAY",
+  "trigger_status": "ACTIVE",
+  "event_type_code": "APICreated",
+  "event_data": {
+    "name": "my-api",
+    "auth": "IAM",
+    "path": "/my-backend",
+    "match_mode": "SWA",
+    "type": 1,
+    "protocol": "HTTPS",
+    "req_method": "ANY",
+    "func_info": { "timeout": 5000 },
+    "instance_id": "<apig-instance-id>",
+    "group_id": "<api-group-id>",
+    "sl_domain": "<sl-domain>",
+    "env_name": "RELEASE",
+    "env_id": "<env-id>"
+  }
+}
+EOF
+hcloud FunctionGraph CreateFunctionTrigger \
+  --function_urn=<urn> \
+  --cli-region=<region> \
+  --project_id=<project_id> \
+  --cli-jsonInput=trigger.json
+```
+
+## List / Delete Triggers
+
+```bash
+hcloud FunctionGraph ListFunctionTriggers --function_urn=<urn>
+hcloud FunctionGraph DeleteFunctionTrigger --function_urn=<urn> --trigger_type_code=<type> --trigger_id=<id>
+```
+
+> Deleting a trigger does NOT cascade-delete the associated APIG API. After `DeleteFunctionTrigger`, also run `hcloud APIG ListApisV2 --instance_id=<id>` and delete orphaned APIs to avoid resource residue.
+>
+> **APIG event format**: When using DEDICATEDGATEWAY, the event body is Base64 encoded and uses a non-standard structure. See `apig-event-format.md` for handler templates.

package/plugins/huaweicloud-core/skills/huawei-gaussdb/SKILL.md

@@ -1,56 +1,56 @@
----
-name: huawei-gaussdb
-description: "Use when creating or managing GaussDB distributed database on Huawei Cloud. Covers GaussDB(for MySQL), GaussDB(for openGauss), sharding, HTAP. Triggers: GaussDB, distributed database, sharding, openGauss, HTAP. NOT for: single RDS (use huawei-rds)."
-version: 1
----
-
-# Huawei Cloud GaussDB
-
-**STOP - Do not answer from general knowledge.** Follow the procedure below.
-
-Always run `hcloud GaussDB <Operation> --help` before constructing commands to discover exact parameter names and requirements.
-
-## Overview
-
-Domain expertise for GaussDB. Covers instance lifecycle, databases, backups, configurations, and shard/readonly node management.
-
-## Critical Warnings
-
-| Trap | Why |
-|------|-----|
-| Shard key permanent | Once set, shard key cannot be changed |
-| Minimum nodes | Distributed GaussDB requires at least 3 nodes for production |
-| Engine version pinned | MySQL-compatible vs openGauss are separate products |
-
-## Common Workflows
-
-| Task | Operation |
-|------|-----------|
-| List instances | `ListInstances --cli-region=<r> --project_id=<p>` |
-| Show instance | `ShowInstance --cli-region=<r> --project_id=<p>` |
-| List flavors | `ListFlavors --cli-region=<r> --project_id=<p>` |
-| Create instance | `CreateInstance --cli-region=<r> --project_id=<p>` |
-| Delete instance | `DeleteInstance --cli-region=<r> --project_id=<p>` |
-| Create backup | `CreateGaussMySqlBackup --cli-region=<r> --project_id=<p>` |
-| Add readonly node | `AddReadonlyNode --cli-region=<r> --project_id=<p>` |
-| Add shard | `AddShardingNode --cli-region=<r> --project_id=<p>` |
-| Manage database | `AddDatabasePermission --cli-region=<r> --project_id=<p>` |
-
-Discover exact parameters with `--help` before executing any command.
-
-## Troubleshooting
-
-| Error | Fix |
-|-------|-----|
-| Instance creation fails | Check VPC/subnet availability and flavor capacity |
-| Connection refused | SG missing database port |
-
-## Security
-
-- MUST use security groups for database access
-- MUST enable SSL for connections
-
-## Cross-Skill References
-
-- **VPC/Subnet/Security Group**: See `huawei-vpc`
-- **Backup/CBR**: See `huawei-cbr`
+---
+name: huawei-gaussdb
+description: "Use when creating or managing GaussDB distributed database on Huawei Cloud. Covers GaussDB(for MySQL), GaussDB(for openGauss), sharding, HTAP. Triggers: GaussDB, distributed database, sharding, openGauss, HTAP. NOT for: single RDS (use huawei-rds)."
+version: 1
+---
+
+# Huawei Cloud GaussDB
+
+**STOP - Do not answer from general knowledge.** Follow the procedure below.
+
+Always run `hcloud GaussDB <Operation> --help` before constructing commands to discover exact parameter names and requirements.
+
+## Overview
+
+Domain expertise for GaussDB. Covers instance lifecycle, databases, backups, configurations, and shard/readonly node management.
+
+## Critical Warnings
+
+| Trap | Why |
+|------|-----|
+| Shard key permanent | Once set, shard key cannot be changed |
+| Minimum nodes | Distributed GaussDB requires at least 3 nodes for production |
+| Engine version pinned | MySQL-compatible vs openGauss are separate products |
+
+## Common Workflows
+
+| Task | Operation |
+|------|-----------|
+| List instances | `ListInstances --cli-region=<r> --project_id=<p>` |
+| Show instance | `ShowInstance --cli-region=<r> --project_id=<p>` |
+| List flavors | `ListFlavors --cli-region=<r> --project_id=<p>` |
+| Create instance | `CreateInstance --cli-region=<r> --project_id=<p>` |
+| Delete instance | `DeleteInstance --cli-region=<r> --project_id=<p>` |
+| Create backup | `CreateGaussMySqlBackup --cli-region=<r> --project_id=<p>` |
+| Add readonly node | `AddReadonlyNode --cli-region=<r> --project_id=<p>` |
+| Add shard | `AddShardingNode --cli-region=<r> --project_id=<p>` |
+| Manage database | `AddDatabasePermission --cli-region=<r> --project_id=<p>` |
+
+Discover exact parameters with `--help` before executing any command.
+
+## Troubleshooting
+
+| Error | Fix |
+|-------|-----|
+| Instance creation fails | Check VPC/subnet availability and flavor capacity |
+| Connection refused | SG missing database port |
+
+## Security
+
+- MUST use security groups for database access
+- MUST enable SSL for connections
+
+## Cross-Skill References
+
+- **VPC/Subnet/Security Group**: See `huawei-vpc`
+- **Backup/CBR**: See `huawei-cbr`