-
Bug
-
Resolution: Done
-
Normal
-
None
-
ACM 2.7.0
-
0
-
False
-
-
False
-
-
-
GRC Sprint 2023-05, GRC Sprint 2023-09, GRC Sprint 2023-10, GRC Sprint 2023-11, GRC Sprint 2023-12, GRC Sprint 2023-13
-
+
-
No
Description of problem:
- The 63 character limit validation for policy name is not working while creating a Policy via CLI.
- Policy creation - Policy name + namespace name can’t go longer than 63
- From CLI, it possible to create a policy with a name like “policy-check-setupjob-setupjob-operator-installer” with no issue; but, while wanting to edit it, we can’t.
- Getting this error: “The combined length of namespace and policy nmabe (namespaceName.policyName) should not exceed 63 characters (see attached screeshot)
Version-Release number of selected component (if applicable):
- ACM 2.7
How reproducible:
- Always
Steps to Reproduce:
- Create policy using yaml file from cli. It gets created successfully.
- Try to edit it from ACM UI.
Actual results:
- Getting this error: “The combined length of namespace and policy nmabe (namespaceName.policyName) should not exceed 63 characters (see attached screeshot)
Expected results:
- While creating policy through CLI, the validation error should have popped up as Policy name + namespace name can’t go longer than 63
Additional info:
- Validation works properly while creating policy through ACM UI.
- duplicates
-
ACM-4394 No validation if name + namespace exceeds 63 characters and Policy applied via CLI or Gitops
-
- Closed
-