2025-09-14 21:52:36 +00:00
|
|
|
|
# NordVPN无法原样导出APP特征
|
|
|
|
|
|
|
|
|
|
|
|
| ID | Creation Date | Assignee | Status |
|
|
|
|
|
|
|----|----------------|----------|--------|
|
|
|
|
|
|
| OMPUB-1275 | 2024-05-07T22:00:56.000+0800 | 张微 | 已关闭 |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
|
|
APP特征导出时，由于不支持引用关系的导出，会导致：
|
|
|
|
|
|
# 两个signature引用同一个object时，导出后会将object拆成两个内容重复的object，并分别根据signature名重新命名两个object
|
|
|
|
|
|
# 一个signature引用了两个object时，导出后会将两个object合并成一个，并根据signature名重新命名object
|
|
|
|
|
|
|
|
|
|
|
|
希望能够将APP特征原样导出和导入**zhangwei** commented on *2024-05-16T15:00:11.822+0800*:
|
|
|
|
|
|
|
|
|
|
|
|
BJ环境升级至api_v24.02_2024051601版本导出App后，可以在192.168.40.219环境导入测试。
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
|
|
**zhangwei** commented on *2024-05-16T15:35:44.557+0800*:
|
|
|
|
|
|
|
|
|
|
|
|
该问题修复后，在目标环境导入App后，将不会对App Signature Name以及Object Name重命名，延用导出源环境的Signature Name以及Object Name。如果目标环境已存在重名的App或者Signature将被覆盖更新。
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
|
|
**zhangwei** commented on *2024-05-28T11:50:46.003+0800*:
|
|
|
|
|
|
|
|
|
|
|
|
M22现场在升级CM API版本至{*}api_v24.02_{color:#ff0000}2024052701{color}{*}之后，需要通过手动执行SQL更新或者在界面再次导入App新建一次Object，将Source TSG Cluster和Destination TSG Cluster的Object同源关联（uuid），以后再次导入更新App才能执行覆盖更新Object。
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
---
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-09-14 22:26:17 +00:00
|
|
|
|
# Attachments
|
2025-09-14 21:52:36 +00:00
|
|
|
|
|
2025-09-14 22:26:17 +00:00
|
|
|
|
Attachment: application.json
|
|
|
|
|
|
[application.json](https://gfwleak.exec.li/admin/geedge-jira/raw/branch/master/attachment/56853/application.json)
|
2025-09-14 21:52:36 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-09-14 22:26:17 +00:00
|
|
|
|
Attachment: image-2024-05-07-21-58-27-109.png
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2025-09-14 21:52:36 +00:00
|
|
|
|
|
