MiFaZhan
59eb34976a
iotlcm-admin-svr：管理后台服务。 - Go module：iotlcm → git.5iot.com/iotlcm-public/iotlcm-admin-svr（729 文件） - 凭据与地址脱敏：JWT signingKey（含代码里的 MustGet 默认值）、 MySQL DSN、Redis 口令、告警邮件发件人邮箱全部改为占位； 私网 IP → 文档地址段；库名 xiujie_admin → iotlcm - 真实手机号/邮箱 → 合法 11 位编造号 / example.com - 移除内部资产：CI 触发器、过时 DDL（sql/db_iotlcm.sql）、 私有依赖 go get 行、明文 registry 登录口令 - 启动 banner 统一 IOTLCM 方块字 + 社区惯例署名 - Dockerfile 改用公共基础镜像 - 拼错的 RADEME.md → README.md，README 重写 - 需要真实数据库的用例改为可用 IOTLCM_TEST_WITH_DB=1 显式启用 - 补 Apache-2.0 LICENSE，LF 行尾 + .gitattributes 数据库 schema 不随本仓发布（生产 DDL 已过时），README 已说明。
77 lines
3.3 KiB
Go
77 lines
3.3 KiB
Go
package model
|
|
|
|
// TrafficUsageSimCard is the basic card data needed when writing usage to TDengine.
|
|
type TrafficUsageSimCard struct {
|
|
Iccid string `json:"iccid"`
|
|
PackageCode string `json:"packageCode"`
|
|
}
|
|
|
|
// TrafficUsageDailyRetryMessage is the retry message for daily traffic usage.
|
|
type TrafficUsageDailyRetryMessage struct {
|
|
UsageMb *float64 `json:"usageMb,omitempty"`
|
|
Attempt int `json:"attempt,omitempty"`
|
|
LastError string `json:"lastError,omitempty"`
|
|
SimKey *SimKey `json:"simKey"`
|
|
Card TrafficUsageSimCard `json:"card"`
|
|
// QueryDate format: yyyyMMdd.
|
|
QueryDate string `json:"queryDate"`
|
|
}
|
|
|
|
// TrafficUsageMonthlyRetryMessage is the retry message for monthly traffic usage.
|
|
type TrafficUsageMonthlyRetryMessage struct {
|
|
UsageMb *float64 `json:"usageMb,omitempty"`
|
|
Attempt int `json:"attempt,omitempty"`
|
|
LastError string `json:"lastError,omitempty"`
|
|
SimKey *SimKey `json:"simKey"`
|
|
Card TrafficUsageSimCard `json:"card"`
|
|
// QueryDate format: yyyyMM.
|
|
QueryDate string `json:"queryDate"`
|
|
}
|
|
|
|
// TrafficUsageMonthlyStartMessage starts one full monthly usage run.
|
|
// Admin publishes this command; Worker owns the card scan and Redis production.
|
|
// A nil Scope (or one whose channels normalize to empty) is a full sync.
|
|
type TrafficUsageMonthlyStartMessage struct {
|
|
RunID string `json:"runId"`
|
|
Operation string `json:"operation"`
|
|
QueryMonth string `json:"queryMonth"`
|
|
TriggeredAt string `json:"triggeredAt"`
|
|
Scope *SyncScope `json:"scope,omitempty"`
|
|
}
|
|
|
|
// TrafficUsageDailyStartMessage starts one full daily usage run.
|
|
// Admin publishes this command; Worker owns the card scan and Redis production.
|
|
// A nil Scope (or one whose channels normalize to empty) is a full sync.
|
|
// QueryDate is yyyyMMdd.
|
|
type TrafficUsageDailyStartMessage struct {
|
|
RunID string `json:"runId"`
|
|
Operation string `json:"operation"`
|
|
QueryDate string `json:"queryDate"`
|
|
TriggeredAt string `json:"triggeredAt"`
|
|
Scope *SyncScope `json:"scope,omitempty"`
|
|
}
|
|
|
|
// OperationPreviousDayUsageFullSync identifies a daily usage run. Admin and
|
|
// Worker must agree on this string: it is the operation recorded on the run and
|
|
// the value Worker maps to the traffic_usage_daily sync kind.
|
|
const OperationPreviousDayUsageFullSync = "previous_day_usage_full_sync"
|
|
|
|
// TrafficUsageMonthlyHistoryStartMessage starts one full monthly usage history
|
|
// run. It writes the TDengine monthly table, which is a different target from
|
|
// TrafficUsageMonthlyStartMessage (the MySQL current-month snapshot).
|
|
//
|
|
// QueryMonth is yyyyMM and names the month being backfilled, which is the
|
|
// previous month rather than the current one.
|
|
type TrafficUsageMonthlyHistoryStartMessage struct {
|
|
RunID string `json:"runId"`
|
|
Operation string `json:"operation"`
|
|
QueryMonth string `json:"queryMonth"`
|
|
TriggeredAt string `json:"triggeredAt"`
|
|
Scope *SyncScope `json:"scope,omitempty"`
|
|
}
|
|
|
|
// OperationPreviousMonthUsageFullSync identifies a monthly usage history run.
|
|
// It is deliberately distinct from current_month_usage_full_sync, which fills
|
|
// the MySQL current-month snapshot instead of the TDengine monthly table.
|
|
const OperationPreviousMonthUsageFullSync = "previous_month_usage_full_sync"
|