"Component.DeleteNamespace.PublicContent":"Deleting Namespace will cause the instance can't get the configuration of this Namespace. Are you sure you want to delete it?",
"Component.DeleteNamespace.PublicContent":"Deleting namespace will cause the instances unable to get the configuration of this namespace. Are you sure to delete it?",
"Component.DeleteNamespace.PrivateContent":"Deleting a private Namespace will cause the instance can’t get the configuration of this Namespace, and the page will prompt the missing Namespace (unless the AppNamespace is deleted by Admin tool). Are you sure you want to delete it?",
"Component.DeleteNamespace.PrivateContent":"Deleting a private Namespace will cause the instances unable to get the configuration of this namespace, and the page will prompt 'missing namespace' (unless the AppNamespace is deleted by admin tool). Are you sure to delete it?",
"Component.ConfigItem.ItemValueTips":"Note: Hidden characters (Spaces, Newline, Tab) easily cause configuration errors. If you need to check hidden characters in Value, Click here",
"Component.ConfigItem.ItemValueTips":"Note: Hidden characters (Spaces, Newline, Tab) easily cause configuration errors. If you want to check hidden characters in Value, please click",
"Component.Namespace.Branch.NoPermissionTips":"You are not the administrator of the project, and you do not have editing or releasing right for the Namespace. You cannot check the configuration.",
"Component.Namespace.Branch.NoPermissionTips":"You are not this project's administrator, nor you have edit or release permission for the namespace. Thus you cannot view the configuration.",
"Component.Namespace.MasterBranch.Body.ModifyItem":"Modify the Grayscale Configuration",
"Component.Namespace.MasterBranch.Body.ModifyItem":"Modify the grayscale configuration",
"Component.Namespace.Branch.GrayScaleRule.NoPermissonTips":"You do not have the right to edit grayscale rule. Only those who have the right to modify or release namespace can edit grayscale rule. If you need to edit grayscale rule, please contact the project administrator to apply for the permission.",
"Component.Namespace.Branch.GrayScaleRule.NoPermissionTips":"You do not have the permission to edit grayscale rule. Only those who have the permission to edit or release the namespace can edit grayscale rule. If you need to edit grayscale rule, please contact the project administrator to apply for the permission.",
"Component.Namespace.Header.Title.PrivateTips":"The configuration of private namespace ({{namespace.baseInfo.namespaceName}}) can be only read by clients whose AppId is {{appId}}",
"Component.Namespace.Header.Title.PrivateTips":"The configuration of private namespace ({{namespace.baseInfo.namespaceName}}) can be only fetched by clients whose AppId is {{appId}}",
"Component.Namespace.Header.Title.ExtendTips":"The configuration of namespace ({{namespace.baseInfo.namespaceName}}) will override the configuration of the public namespace, and the combined configuration can only be read by clients whose AppId is {{appId}}.",
"Component.Namespace.Header.Title.ExtendTips":"The configuration of namespace ({{namespace.baseInfo.namespaceName}}) will override the configuration of the public namespace, and the combined configuration can only be fetched by clients whose AppId is {{appId}}.",
"Component.Namespace.Master.Items.NoPermissionTips":"You are not the administrator of the project, and you do not have editing or releasing authority for the Namespace. You cannot check the configuration information.",
"Component.Namespace.Master.Items.NoPermissionTips":"You are not this project's administrator, nor you have edit or releas permission for the namespace. Thus you cannot view the configuration.",
"Component.Namespace.Master.Items.Body.ItemsNoPublishedTips":"Tips: This namespace has never been released. Apollo client will not be able to get the configuration and record 404 log information. Please release it in time.",
"Component.Namespace.Master.Items.Body.ItemsNoPublishedTips":"Tips: This namespace has never been released. Apollo client will not be able to fetch the configuration and will record 404 log information. Please release it in time.",
"Component.Namespace.Master.Items.Body.FilterByKey":"Input key for filtering",
"Component.Namespace.Master.Items.Body.FilterByKey":"Input key to filter",
"Component.Namespace.Master.Items.Body.Public.NoPublicNamespaceTips1":"Owner of the current public namespace",
"Component.Namespace.Master.Items.Body.Public.NoPublicNamespaceTips1":"Owner of the current public namespace",
"Component.Namespace.Master.Items.Body.Public.NoPublicNamespaceTips2":"No association with this namespace, please contact the owner of {{namespace. parentAppId}} to associate with this namespace in the {{namespace. parentAppId}} project.",
"Component.Namespace.Master.Items.Body.Public.NoPublicNamespaceTips2":"hasn't associated this namespace, please contact the owner of {{namespace.parentAppId}} to associate this namespace in the {{namespace.parentAppId}} project.",
"Component.PublishDeny.Tips1":"You can't release ~{{env}} Editing environment configuration and releasing must be for different people, please ask someone who has the releasing authority of this namespace to operate the release.~",
"Component.PublishDeny.Tips1":"You can't release! The operators to edit and release the configurations in {{env}} environment must be different, please find someone else who has the release permission of this namespace to do the release operation.",
"Component.PublishDeny.Tips2":"(If it is non working time or special situations, you may release by clicking the <mark> Emergency Release </mark> button.)",
"Component.PublishDeny.Tips2":"(If it is non working time or a special situation, you may release by clicking the 'Emergency Release' button.)",
"Component.Publish.Tips":"(Only the released configuration will be accessed by the client, and this release will only work in the current environment: {{env}})",
"Component.Publish.Tips":"(Only the released configurations can be fetched by clients, and this release will only be applied to the current environment: {{env}})",
"Component.Rollback.Tips":"This operation will roll back to the previous released version, and the current version is invalid, but no impact on the modifying configuration. You can check the current version on the releasing history page",
"Component.Rollback.Tips":"This operation will roll back to the last released version, and the current version is abandoned, but there is no impact to the currently editing configurations. You may view the currently effective version in the release history page",
"Cluster.Tips.1":"By adding clusters, the same program can use different configuration in different clusters (such as different data centers)",
"Cluster.Tips.1":"By adding clusters, the same program can use different configuration in different clusters (such as different data centers)",
"Cluster.Tips.2":"If the different clusters use the same configuration, there is no need to create clusters",
"Cluster.Tips.2":"If the different clusters use the same configuration, there is no need to create clusters",
"Cluster.Tips.3":"By default, Apollo reads IDC attributes in /opt/settings/server.properties(Linux) or C:\\opt\\settings\\server.properties(Windows) files on the machine as cluster names, such as SHAJQ (Jinqiao Data Center), SHAOY (Ouyang Data Center)",
"Cluster.Tips.3":"By default, Apollo reads IDC attributes in /opt/settings/server.properties(Linux) or C:\\opt\\settings\\server.properties(Windows) files on the machine as cluster names, such as SHAJQ (Jinqiao Data Center), SHAOY (Ouyang Data Center)",
"Cluster.Tips.4":"The cluster name created at here needs to be consistent with the IDC attribute in server.properties on the machine",
"Cluster.Tips.4":"The cluster name created here should be consistent with the IDC attribute in server.properties on the machine",
"Cluster.CreaterNameTips":"(Deploy clusters such as SHAJQ, SHAOY or customized clusters such as SHAJQ-xx, SHAJQ-yy)",
"Cluster.CreateNameTips":"(Cluster names such as SHAJQ, SHAOY or customized clusters such as SHAJQ-xx, SHAJQ-yy)",
"Cluster.ChooseEnvironment":"Select the environment",
"Cluster.ChooseEnvironment":"Environment",
"Cluster.LoadingEnvironmentError":"Error in loading environment information",
"Cluster.LoadingEnvironmentError":"Error in loading environment information",
"Config.ClusterIsDefualtTipContent":"All instances that do not belong to the'{{name}}'cluster will use the default cluster (current page) configuration, and those that belong to the'{{name}}' cluster will use the corresponding cluster configuration!",
"Config.ClusterIsDefaultTipContent":"All instances that do not belong to the '{{name}}' cluster will fetch the default cluster (current page) configuration, and those that belong to the '{{name}}' cluster will use the corresponding cluster configuration!",
"Config.ClusterIsCustomTipContent":"Instances belonging to the'{{name}}'cluster only use the configuration of the'{{name}}' cluster (the current page), and the default cluster configuration is used only when the corresponding namespace has not been published in the current cluster.",
"Config.ClusterIsCustomTipContent":"Instances belonging to the '{{name}}' cluster will only fetch the configuration of the '{{name}}' cluster (the current page), and the default cluster configuration will only be fetched when the corresponding namespace has not been released in the current cluster.",
"Config.HasNotPublishNamespace":"The following environment/cluster has unpublished configuration, the client can not get unpublished configuration, please publish in time.",
"Config.HasNotPublishNamespace":"The following environment/cluster has unreleased configurations, the client will not fetch the unreleased configurations, please release them in time.",
"Config.DeleteItem.DialogContent":"You are deleting the configuration whose Key is <b>'{{config.key}} </b> Value is <b>'{{config.value}} </b>. <br> Are you sure you want to delete the configuration?",
"Config.DeleteItem.DialogContent":"You are deleting the configuration whose Key is <b>'{{config.key}}'</b> Value is <b>'{{config.value}}'</b>. <br> Are you sure to delete the configuration?",
"Config.PublishNoPermission.DialogContent":"You do not have publishing permissions. ~Ask the Project Administrator'{{masterUsers}}'to assign publishing permissions.",
"Config.PublishNoPermission.DialogContent":"You do not have release permission. Please ask the project administrators '{{masterUsers}}' to authorize release permission.",
"Config.ModifyNoPermission.DialogTitle":"Application for Configuration Permission",
"Config.ModifyNoPermission.DialogTitle":"Apply for Configuration Permission",
"Config.ModifyNoPermission.DialogContent":"Assign editing or publishing permissions to project administrator'{{masterUsers}}'",
"Config.ModifyNoPermission.DialogContent":"Please ask the project administrators '{{masterUsers}}' to authorize release or edit permission.",
"Config.MasterNoPermission.DialogTitle":"Application for Configuration Permission",
"Config.MasterNoPermission.DialogTitle":"Apply for Configuration Permission",
"Config.MasterNoPermission.DialogContent":"You are not a project administrator. Only project administrators have the right to add clusters and namespaces. For administrator privileges, ask the project administrator'{{masterUsers}}'to assign administrator privileges",
"Config.MasterNoPermission.DialogContent":"You are not this project's administrator. Only project administrators have the permission to add clusters and namespaces. Please ask the project administrators '{{masterUsers}}' to assign administrator permission",
"Config.UpdateRuleTips.DialogContent":"Grayscale rules are in effect, but it is found that grayscale versions have unpublished configurations that require manual grayscale publishing to take effect.",
"Config.UpdateRuleTips.DialogContent":"Grayscale rules are in effect. However there are unreleased configurations in grayscale version, they won't be effective until a manual grayscale release is performed.",
"Config.MergeAndReleaseDeny.DialogContent":"The main version of namespace has unpublished configuration. Please publish the main version configuration first.",
"Config.MergeAndReleaseDeny.DialogContent":"The main version has unreleased configuration. Please release the main version first.",
"Config.GrayReleaseWithoutRulesTips.DialogContent":"The grayscale version has not been configured with any grayscale rules. Please configure the grayscale rules.",
"Config.GrayReleaseWithoutRulesTips.DialogContent":"The grayscale version has not configured any grayscale rule. Please configure the grayscale rules.",
"Config.DeleteNamespaceDenyForMasterInstance.DialogContent":"It was found that <B>'{{delete Namespace Context. namespace. instancesCount}}'</b> instances were using Namespace ('{{delete Namespace Context. namespace. baseInfo. namespace Name}}'), and deleting Namespace would result in instances not getting configuration. <br> Please go to <ins> \"Instance List\"</ins> to confirm the instance information. If you confirm that the relevant instances are no longer using the Namespace configuration, you can contact the Apollo responsible person to delete the instance information (Instance Config) or wait for the instance to expire automatically 24 hours before deleting.",
"Config.DeleteNamespaceDenyForMasterInstance.DialogContent":"There are <b>'{{deleteNamespaceContext.namespace.instancesCount}}'</b> instances using namespace ('{{deleteNamespaceContext.namespace.baseInfo.namespaceName}}'), and deleting namespace would cause those instances failed to fetch configuration. <br> Please go to <ins> \"Instance List\"</ins> to confirm the instance information. If you confirm that the relevant instances are no longer using the namespace configuration, you can contact the Apollo administrators to delete the instance information (Instance Config) or wait for the instance to expire automatically 24 hours before deletion.",
"Config.DeleteNamespaceDenyForBranchInstance.DialogContent":"It was found that <B>'{{delete Namespace Context. namespace. branch. latest Release Instances. total}}'</b> instances were using the gray level version of Namespace ('{{delete Namespace Context. namespace. baseInfo. namespace Name}}') configuration, and deleting Namespace would result in instances not getting the configuration. <br> Please go to <ins> \"gray version\"=> \"instance list\"</ins> to confirm the instance information. If you confirm that the relevant instances are no longer using the Namespace configuration, you can contact the Apollo responsible person to delete the instance information (Instance Config) or wait for the instance to expire automatically 24 hours before deleting.",
"Config.DeleteNamespaceDenyForBranchInstance.DialogContent":"There are <b>'{{deleteNamespaceContext.namespace.branch.latestReleaseInstances.total}}'</b> instances using the graysacle version of namespace ('{{deleteNamespaceContext.namespace.baseInfo.namespaceName}}') configuration, and deleting Namespace would cause those instances failed to fetch configuration. <br> Please go to <ins> \"Grayscale Version\"=> \"Instance List\"</ins> to confirm the instance information. If you confirm the relevant instances are no longer using the namespace configuration, you can contact the Apollo administrators to delete the instance information (Instance Config) or wait for the instance to expire automatically 24 hours before deletion.",
"Config.CreateBranchTips.DialogContent":"By creating gray level version, you can do gray level test for some configurations <br> gray level process as follows: <br> (1) create gray level version <br> (2) configure gray level configuration items <br> (3) configure gray level rules. If it is private namespace, it can be gray level according to the IP of client, if it is public name. Gray level <br> 4. Gray level publishing <br> gray level version has two final results: <b> full publishing and abandoning gray level </b> <br> <b> full publishing </b>: gray level configuration is combined with the main version and distributed, all clients will use the combined configuration <br> <b> abandon gray level </b>: remove gray. In degree version, all clients will use the configuration <br> of the main version: <br> 1. If the gray level version has been published, then the gray level rules will be changed immediately without the need for gray level publication again.",
"Config.CreateBranchTips.DialogContent":"By creating grayscale version, you can do grayscale test for some configurations. <br> Grayscale process is as follows: <br> 1. Create grayscale version <br> 2. Configure grayscale configuration items <br> 3. Configure grayscale rules. If it is a private namespace, it can be grayed according to the IP of client. If it is a public namespace, it can be grayed accodring to both appid and the IP. <br> 4. Grayscale release <br> Grayscale version has two final results: <b> Full release and Abandon grayscale</b> <br> <b>Full release</b>: grayscale configurations are merged with the main version and released, all clients will use the merged configurations <br> <b> Abandon grayscale</b>: Delete grayscale version. All clients will use the configurations of the main version<br> Notice: <br> 1. If the grayscale version has been released, then the grayscale rules will be effective immediately without the need to release grayscale configuration again.",
"Config.ProjectMissEnvInfos":"Current project has environment missing, please click on the left side of the page to fill in the missing environment to fill in the data.",
"Config.ProjectMissEnvInfos":"There are missing environments in the current project, please click \"Recover Environments\" on the left side of the page to do the recovery.",
"Config.ProjectMissNamespaceInfos":"There is a missing Namespace in the current environment. Please click \"Fill in Namespace\" on the left side of the page to fill in the data.",
"Config.ProjectMissNamespaceInfos":"There are missing namespaces in the current environment. Please click \"Recover Namespaces\" on the left side of the page to do the recovery.",
"Config.SystemError":"System error, please try again or contact the system manager",
"Config.SystemError":"System error, please try again or contact the system administrator",
"Config.BranchDeleteFailed":"Failed to delete branch",
"Config.DeleteNamespaceFailedTips":"The following applications are associated with this public Namespace and must delete all associated Namespace before deleting the public Namespace",
"Config.DeleteNamespaceFailedTips":"The following projects are associated with this public namespace and they must all be deleted deleting the public Namespace",
"Config.DeleteNamespaceNoPermissionFailedTitle":"Failed to delete",
"Config.DeleteNamespaceNoPermissionFailedTips":"You do not have Project Administrator privileges. Only Administrators can delete Namespace. Please find Project Administrator [{{usres}}] to delete Namespace.",
"Config.DeleteNamespaceNoPermissionFailedTips":"You do not have Project Administrator permission. Only Administrators can delete namespace. Please ask Project Administrators [{{usres}}] to delete namespace.",
"Delete.DeleteAppTips":"(Because deleting applications has a large impact, system administrators are only allowed to delete them for the time being. Make sure that no client reads the configuration of the application before deleting it.)",
"Delete.DeleteAppTips":"(Because deleting applications has very large impacts, only system administrators are allowed to delete them for the time being. Make sure that no client fetches the configuration of the application before deleting it.)",
"Delete.AppIdTips":"(Please query application information before deleting)",
"Delete.AppIdTips":"(Please query application information before deleting)",
"Delete.AppInfo":"Application information",
"Delete.AppInfo":"Application information",
"Delete.DeleteCluster":"Delete clusters",
"Delete.DeleteCluster":"Delete clusters",
"Delete.DeleteClusterTips":"(Because deleting the cluster has a large impact, only system administrators are allowed to delete it for the time being. Make sure that no client reads the configuration of the cluster before deleting it.)",
"Delete.DeleteClusterTips":"(Because deleting clusters has very large impacts, only system administrators are allowed to delete them for the time being. Make sure that no client fetches the configuration of the cluster before deleting it.)",
"Delete.EnvName":"Environment Name",
"Delete.EnvName":"Environment Name",
"Delete.ClusterNameTips":"(Please query application cluster information before deleting)",
"Delete.ClusterNameTips":"(Please query cluster information before deletion)",
"Delete.ClusterInfo":"Cluster information",
"Delete.ClusterInfo":"Cluster information",
"Delete.DeleteNamespace":"Delete AppNamespace",
"Delete.DeleteNamespace":"Delete AppNamespace",
"Delete.DeleteNamespaceTips":"(Note that Namespace and AppNamespace in all environments will be deleted! If you just want to delete the Namespace of an environment, let the user delete it on the project page!",
"Delete.DeleteNamespaceTips":"(Note that Namespace and AppNamespace in all environments will be deleted! If you just want to delete the namespace of some environment, let the user delete it on the project page!",
"Delete.DeleteNamespaceTips2":"At present, users can delete the associated Namespace and private Namespace by themselves, but they can not delete the meta-information of AppNamespace. Because deleting AppNamespace has a large impact, it is only allowed to be deleted by system administrators for the time being. For public Namespace, it is necessary to ensure that the associated AppNamespace is not applied.",
"Delete.DeleteNamespaceTips2":"Currently users can delete the associated namespace and private namespace by themselves, but they can not delete the AppNamespace. Because deleting AppNamespace has very large impacts, it is only allowed to be deleted by system administrators for the time being. For public Namespace, it is necessary to ensure that no application associates the AppNamespace",
"Delete.AppNamespaceName":"AppNamespace name",
"Delete.AppNamespaceName":"AppNamespace name",
"Delete.AppNamespaceNameTips":"(For namespaces of non-property types, add type suffixes, such as apollo.xml)",
"Delete.AppNamespaceNameTips":"(For non-properties namespaces, please add the suffix, such as apollo.xml)",
"Delete.ConfirmDeleteNamespace":"Confirm to delete AppNamespace and Namespace for all environments? AppId:'{{appId}}'environment:'All environments' AppNamespace name:'{{namespace}}'",
"Delete.ConfirmDeleteNamespace":"Are you sure to delete AppNamespace and Namespace for all environments? AppId: '{{appId}}' environment: 'All environments' AppNamespace name: '{{namespace}}'",
"Namespace.Title":"New Namespace",
"Namespace.Title":"New Namespace",
"Namespace.UnderstandMore":"(Click to learn more about Namespace)",
"Namespace.UnderstandMore":"(Click to learn more about Namespace)",
"Namespace.Link.Tips1":"Applications can override the configuration of a common Namespace by associating a common namespace",
"Namespace.Link.Tips1":"Applications can override the configuration of a public namespace by associating a public namespace",
"Namespace.Link.Tips2":"If the application does not need to override the configuration of the common Namespace, then there is no need to associate the common Namespace",
"Namespace.Link.Tips2":"If the application does not need to override the configuration of the public namespace, then there is no need to associate the public namespace",
"Namespace.CreatePublic.Tips1":"The configuration of the public Namespace can be read by any project",
"Namespace.CreatePublic.Tips1":"The configuration of the public Namespace can be fetched by any application",
"Namespace.CreatePublic.Tips2":"Configuration of common components can be achieved by creating a common Namespace, and the need for multiple applications to share the same configuration can be achieved.",
"Namespace.CreatePublic.Tips2":"Configuration of public components or the need for multiple applications to share the same configuration can be achieved by creating a public namespace.",
"Namespace.CreatePublic.Tips3":"If other applications need to cover the configuration of the public part, you can associate the public Namespace with other applications, and then configure the configuration that needs to be covered in the associated Namespace.",
"Namespace.CreatePublic.Tips3":"If other applications need to override the configuration of the public namespace, you can associate the public namespace in other applications, and then configure the configuration that needs to be overridden in the associated namespace.",
"Namespace.CreatePublic.Tips4":"If other applications do not need to cover the configuration of common parts, then there is no need to associate common Namespace with other applications.",
"Namespace.CreatePublic.Tips4":"If other applications do not need to override the configuration of public namespace, then there is no need to associate public namespace in other applications.",
"Namespace.CreatePrivate.Tips1":"The configuration of private Namespace can only be obtained by the application to which it belongs.",
"Namespace.CreatePrivate.Tips1":"The configuration of a private Namespace can only be fetched by the application to which it belongs.",
"Namespace.CreatePrivate.Tips2":"Group management configuration can be achieved by creating a private Namespace",
"Namespace.CreatePrivate.Tips2":"Group management configuration can be achieved by creating a private namespace",
"Namespace.CreatePrivate.Tips3":"The format of private Namespace can be xml, yml, yaml, json, txt. You can get the content of Namespace in non-property format through the ConfigFile interface in apollo-client.",
"Namespace.CreatePrivate.Tips3":"The format of private namespaces can be xml, yml, yaml, json, txt. You can get the content of namespace in non-property format through the ConfigFile interface in apollo-client.",
"Namespace.CreatePrivate.Tips4":"The 1.3.0 and above versions of apollo-client provide better support for yaml/yml. Config objects can be obtained directly through ConfigService.getConfig (\"someNamespace.yml\"), or through @EnableApolloConfig (\"someNamespace.yml\") or apollo.bootstrap.namespaces=Namespace.yml to inject YML configuration into Spring/Spring Boot. Go in",
"Namespace.CreatePrivate.Tips4":"The 1.3.0 and above versions of apollo-client provide better support for yaml/yml. Config objects can be obtained directly through ConfigService.getConfig(\"someNamespace.yml\"), or through @EnableApolloConfig(\"someNamespace.yml\") or apollo.bootstrap.namespaces=someNamespace.yml to inject YML configuration into Spring/Spring Boot",
"Namespace.CreateNamespcae":"Create Namespace",
"Namespace.CreateNamespace":"Create Namespace",
"Namespace.AssociationPublicNamespcae":"Associated Public Namespace",
"Namespace.AssociationPublicNamespace":"Associate Public Namespace",
"Namespace.ChooseCluster":"Select Cluster",
"Namespace.ChooseCluster":"Select Cluster",
"Namespace.NamespaceName":"Name",
"Namespace.NamespaceName":"Name",
"Namespace.AutoAddDepartmentPrefix":"Automatically add Department prefix",
"Namespace.AutoAddDepartmentPrefix":"Add department prefix",
"Namespace.AutoAddDepartmentPrefixTips":"(The name of a public Namespace needs to be globally unique, and adding a department prefix helps ensure global uniqueness)",
"Namespace.AutoAddDepartmentPrefixTips":"(The name of a public namespace needs to be globally unique, and adding a department prefix helps ensure global uniqueness)",
"Namespace.LoadingAppInfoError":"Failed to load App information",
"Namespace.PleaseChooseCluster":"Select Cluster",
"Namespace.PleaseChooseCluster":"Select Cluster",
"Namespace.ChecknamespaceNameLengthTip":"The namespace name should not be greater than 100 characters. Department prefix:'{{department Length}}'characters, name {{namespace Length}} characters",
"Namespace.CheckNamespaceNameLengthTip":"The namespace name should not be longer than 32 characters. Department prefix:'{{departmentLength}}' characters, name {{namespaceLength}} characters",
"SericeConfig.Title":"Application Configuration",
"ServiceConfig.Title":"System Configuration",
"SericeConfig.Tips":"(Maintain Apollo PortalDB.ServerConfig table data, override configuration items if they already exist, or create configuration items. Configuration updates take effect automatically in a minute)",
"ServiceConfig.Tips":"(Maintain Apollo PortalDB.ServerConfig table data, will override configuration items if they already exist, or create configuration items. Configuration updates take effect automatically in a minute)",
"SericeConfig.Key":"Key",
"ServiceConfig.Key":"Key",
"SericeConfig.KeyTips":"(Please query the configuration information before modifying the configuration)",
"ServiceConfig.KeyTips":"(Please query the configuration information before modifying the configuration)",
"SericeConfig.Value":"Value",
"ServiceConfig.Value":"Value",
"SericeConfig.Comment":"Comment",
"ServiceConfig.Comment":"Comment",
"SericeConfig.Saved":"Successful Preservation",
"ServiceConfig.Saved":"Save Successfully",
"SericeConfig.SaveFailed":"Save failed",
"ServiceConfig.SaveFailed":"Failed to Save",
"SericeConfig.PleaseEnterKey":"Please enter key",
"ServiceConfig.PleaseEnterKey":"Please enter key",
"SericeConfig.KeyNotExistsAndCreateTip":"Key:'{{key}}'does not exist. Click Save to create the configuration item.",
"ServiceConfig.KeyNotExistsAndCreateTip":"Key: '{{key}}' does not exist. Click Save to create the configuration item.",
"SericeConfig.KeyExistsAndSaveTip":"Key:'{{key}}'already exists. Clicking Save will override the configuration item.",
"ServiceConfig.KeyExistsAndSaveTip":"Key: '{{key}}' already exists. Click Save will override the configuration item.",
"SystemInfo.Title":"system information",
"SystemInfo.Title":"System Information",
"SystemInfo.SystemVersion":"System version",
"SystemInfo.SystemVersion":"System version",
"SystemInfo.Tips1":"The environment list comes from the <strong>apollo.portal.envs</strong> configuration in Apollo PortalDB.ServerConfig, and can be accessed to <a href=\"{{serverConfigUrl}}\"> system parameters </a> page configuration. More information can be referred to <a href=\"{{wikiUrl}}\"> distributed deployment guide </a> in <strong>apollo.portal.envs-a supportable environment list.</ strong> chapters.",
"SystemInfo.Tips1":"The environment list comes from the <strong>apollo.portal.envs</strong> configuration in Apollo PortalDB.ServerConfig, and can be configured in <a href=\"{{serverConfigUrl}}\">System Configuration</a> page. For more information, please refer the <strong>apollo.portal.envs - supportable environment list</strong> section in <a href=\"{{wikiUrl}}\">Distributed Deployment Guide</a>.",
"SystemInfo.Tips2":"The Meta server address shows the meta server information for this environment configuration. For more information, please refer to the <strong> meta service information for configuring apollo-portal </strong> section in <a href=\"{{wikiUrl}}\"> Distributed Deployment Guide </a>.",
"SystemInfo.Tips2":"The meta server address shows the meta server information for this environment configuration. For more information, please refer the <strong>Configuring meta service information for apollo-portal</strong> section in <a href=\"{{wikiUrl}}\">Distributed Deployment Guide</a>.",
"SystemInfo.Active":"Active",
"SystemInfo.Active":"Active",
"SystemInfo.ActiveTips":"(Current environment status is abnormal, please check with the system information below and Check Health results of AdminService)",
"SystemInfo.ActiveTips":"(Current environment status is abnormal, please diagnose with the system information below and Check Health results of AdminService)",
"SystemInfo.MetaServerAddress":"Meta server address",
"SystemInfo.MetaServerAddress":"Meta server address",
"SystemRole.AddCreateAppRoleToUser":"Create application privileges for users",
"SystemRole.AddCreateAppRoleToUser":"Create application permission for users",
"SystemRole.AddCreateAppRoleToUserTips":"(When role.create-application.enabled=true is set in system configurations, only super admin and those accounts with Create application privileges can create application)",
"SystemRole.AddCreateAppRoleToUserTips":"(When role.create-application.enabled=true is set in system configurations, only super admin and those accounts with Create application permission can create application)",
"SystemRole.ChooseUser":"User Selection",
"SystemRole.ChooseUser":"Select User",
"SystemRole.Add":"Add to",
"SystemRole.Add":"Add",
"SystemRole.AuthorizedUser":"Users with privileges",
"SystemRole.AuthorizedUser":"Users with permission",
"SystemRole.ModifyAppAdminUserTips":"(When role.manage-app-master.enabled=true is set in system configurations, only super admin and those accounts with application administrator allocation permissions can modify the application's administrators)",
"SystemRole.ModifyAppAdminUserTips":"(When role.manage-app-master.enabled=true is set in system configurations, only super admin and those accounts with application administrator allocation permissions can modify the application's administrators)",
"SystemRole.AppIdTips":"(Please query the application information first)",
"SystemRole.AppIdTips":"(Please query the application information first)",
"SystemRole.AppInfo":"Application information",
"SystemRole.AppInfo":"Application information",
"SystemRole.AllowAppMasterAssignRole":"Allow this user to add Master as an administrator",
"SystemRole.AllowAppMasterAssignRole":"Allow this user to add Master as an administrator",
"SystemRole.DeleteAppMasterAssignRole":"Prohibit this user from adding Master as an administrator",
"SystemRole.DeleteAppMasterAssignRole":"Disallow this user to add Master as an administrator",
"SystemRole.IsRootUser":"The current page is open only to Apollo administrators",
"SystemRole.IsRootUser":"The current page is only accessible to Apollo administrators",
"SystemRole.PleaseChooseUser":"Please select a user name",
"SystemRole.PleaseChooseUser":"Please select a user",
"SystemRole.Added":"Added Successfully",
"SystemRole.Added":"Add Successfully",
"SystemRole.AddFailed":"Failure to add",
"SystemRole.AddFailed":"Failed to add",
"SystemRole.Deleted":"Successful deletion",
"SystemRole.Deleted":"Delete Successfully",
"SystemRole.DeleteFailed":"Delete failed",
"SystemRole.DeleteFailed":"Failed to Delete",
"SystemRole.GetCanCreateProjectUsersError":"Error getting user list with creation project",
"SystemRole.GetCanCreateProjectUsersError":"Error getting user list with create project permission",
"SystemRole.PleaseEnterAppId":"Please enter appId",
"SystemRole.PleaseEnterAppId":"Please enter appId",
"SystemRole.AppIdNotFound":"AppId:'{{appId}}'does not exist!",
"SystemRole.AppIdNotFound":"AppId: '{{appId}}' does not exist!",
"SystemRole.AppInfoContent":"Application name:'{{appName}}'department:'{{departmentName}} ({{departmentId}})'person in charge:'{{ownerName}}",
"SystemRole.DeleteMasterAssignRoleTips":"Verify that the user who deleted AppId:'{{appId}}':'{{userId}}'assigns permissions to the application administrator?",
"SystemRole.DeleteMasterAssignRoleTips":"Are you sure to disallow the user '{{userId}}' to add Master as an administrator for AppId:'{{appId}}'?",
"SystemRole.DeletedMasterAssignRoleTips":"Disallow the user '{{userId}}' to add Master as an administrator for AppId:'{{appId}}' Successfully",
"SystemRole.AllowAppMasterAssignRoleTips":"Verify that the user who added AppId:'{{appId}}':'{{userId}}'assigns the permissions of the application administrator?",
"SystemRole.AllowAppMasterAssignRoleTips":"Are you sure to allow the user '{{userId}}' to add Master as an administrator for AppId:'{{appId}}'?",
"SystemRole.AllowedAppMasterAssignRoleTips":"Users who add AppId:'{{appId}}':'{{userId}}'Allocate Application Administrator's Privileges Successfully",
"SystemRole.AllowedAppMasterAssignRoleTips":"Allow the user '{{userId}}' to add Master as an administrator for AppId:'{{appId}}' Successfully",
"UserMange.Title":"user management",
"UserMange.Title":"User Management",
"UserMange.TitleTips":"(Only valid for the default Spring Security simple authentication method: - Dapollo_profile = github,auth)",
"UserMange.TitleTips":"(Only valid for the default Spring Security simple authentication method: - Dapollo_profile = github,auth)",
"UserMange.UserName":"User name",
"UserMange.UserName":"User Name",
"UserMange.UserNameTips":"If the user name entered does not exist, create a new one. If it already exists, it is updated.",
"UserMange.UserNameTips":"If the user name entered does not exist, will create a new one. If it already exists, then it will be updated.",
"Open.Manage.CreateThirdAppTips":"(Note: Third-party applications can manage configuration through Apollo Open Platform)",
"Open.Manage.CreateThirdAppTips":"(Note: Third-party applications can manage configuration through Apollo Open Platform)",
"Open.Manage.ThirdAppId":"Third party application ID",
"Open.Manage.ThirdAppId":"Third party appId",
"Open.Manage.ThirdAppIdTips":"(Before creating, please check if third-party applications have been applied for)",
"Open.Manage.ThirdAppIdTips":"(Please check if the third-party application has already exists first)",
"Open.Manage.ThirdAppName":"Third party application name",
"Open.Manage.ThirdAppName":"Third party application name",
"Open.Manage.ThirdAppNameTips":"(Suggested format xx-yy-zz example: apollo-server)",
"Open.Manage.ThirdAppNameTips":"(Suggested format xx-yy-zz e.g. apollo-server)",
"Open.Manage.ProjectOwner":"Project Leader",
"Open.Manage.ProjectOwner":"Owner",
"Open.Manage.Create":"Establish",
"Open.Manage.Create":"Create",
"Open.Manage.GrantPermission":"Empowerment",
"Open.Manage.GrantPermission":"Authorization",
"Open.Manage.GrantPermissionTips":"Namespace level permissions include modifying and publishing Namespace. Application level permissions include creating Namespace, modifying or publishing any Namespace under an application.",
"Open.Manage.GrantPermissionTips":"(Namespace level permissions include edit and release namespace. Application level permissions include creating namespace, edit or release any namespace in the application.)",
"Open.Manage.ManagedNamespaceTips":"(For namespaces of non-property types, add type suffixes, such as apollo.xml)",
"Open.Manage.ManagedNamespaceTips":"(For non-properties namespaces, please add the suffix, such as apollo.xml)",
"Open.Manage.GrantType":"Authorization type",
"Open.Manage.GrantType":"Authorization type",
"Open.Manage.GrantType.Namespace":"Namespace",
"Open.Manage.GrantType.Namespace":"Namespace",
"Open.Manage.GrantType.App":"App",
"Open.Manage.GrantType.App":"App",
"Open.Manage.GrantEnv":"Environmental Science",
"Open.Manage.GrantEnv":"Environments",
"Open.Manage.GrantEnvTips":"(If you don't select, all environments have permissions. If you prompt Namespace's role does not exist, open the authorization page of the Namespace to trigger the privilege initialization action.)",
"Open.Manage.GrantEnvTips":"(If you don't select any environment, then will have permissions to all environments.)",
"Open.Manage.PleaseEnterAppId":"Please enter appId",
"Open.Manage.PleaseEnterAppId":"Please enter appId",
"Open.Manage.AppNotCreated":"App ('{{appId}}') was not created, please create it first",
"Open.Manage.AppNotCreated":"App('{{appId}}') does not exist, please create it first",
"Config.History.NoPermissonTips":"You are not the administrator of the project, and you do not have editing or publishing rights for the Namespace. You cannot view the publishing history.",
"Config.History.NoPermissionTips":"You are not this project's administrator, nor you have edit or release permission for the namespace. Thus you cannot view the release history.",
"Config.History.NoPublishHistory":"No release of historical information",
"App.AppNameTips":"(Suggested format xx-yy-zz e.g. apollo-server)",
"App.AppOwnerTips":"(After enabling the application administrator allocation restrictions, the application manager and project administrator default to this account, not optional)",
"App.AppOwnerTips":"(After enabling the application administrator allocation restrictions, the application owner and project administrator are default to current account, not subject to change)",
"App.AppAdminTips1":"(The application manager defaults to project administrator privileges.",
"App.AppAdminTips1":"(The application owner has project administrator permission by default.",
"App.AppAdminTips2":"Project administrators can create Namespace, cluster, and assign user privileges)",
"App.AppAdminTips2":"Project administrators can create namespace, cluster, and assign user permissions)",
"App.Setting.Title":"project management",
"App.Setting.Title":"Manage Project",
"App.Setting.Admin":"Administrators",
"App.Setting.Admin":"Administrators",
"App.Setting.AdminTips":"(Project administrators have the following permissions: 1. Create Namespace 2. Create clusters 3. Manage projects, Namespace permissions)",
"App.Setting.AdminTips":"(Project administrators have the following permissions: 1. Create namespace 2. Create clusters 3. Manage project and namespace permissions)",
"App.Setting.Add":"Add to",
"App.Setting.Add":"Add",
"App.Setting.BasicInfo":"Essential information",
"App.Setting.BasicInfo":"Basic information",
"App.Setting.ProjectName":"entry name",
"App.Setting.ProjectName":"App Name",
"App.Setting.ProjectNameTips":"(Suggested format xx-yy-zz example: apollo-server)",
"App.Setting.ProjectNameTips":"(Suggested format xx-yy-zz e.g. apollo-server)",
