-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
4.7.0
-
Quality / Stability / Reliability
-
False
-
-
False
-
-
-
-
Rox Sprint 4.8G - Global, Rox Sprint 4.8H - Global, Rox Sprint 4.9A - Global, Rox Sprint 4.9B - Global, Rox Sprint 4.9C - Global, Rox Sprint 4.9D - Global, Rox Sprint 4.9E - Global, Rox Sprint 4.9F - Global, Rox Sprint 4.9G - Global, Rox Sprint 4.9H - Global, Rox Sprint 4.10A - Global, Rox Sprint 4.9I - Global
-
0
The following three policy criteria provide the exact same output:
- Volume type
- Volume Source (path)
- Volume Destination (path)
Read-only volume 'my-hostpath-volume' has source '/source-data', destination '/mnt/data', and type 'HostPath'
This information is valuable but what impossible to know which one of these is the reason why this violation has fired.
- Suggest to highlight the reason but don't eliminate the other two volume fields.
- Please add the word "path" to say "source path" and "destination path"
For example in the case of Volume Source Path criterion we would say something like
VIOLATION: volume 'my-hostpath-volume' has source path '/source-data'
INFO: Read-only volume 'my-hostpath-volume' has source path '/source-data', destination path '/mnt/data', and type 'HostPath'
- clones
-
ROX-28058 Policy editor allows the selection of Build (+Deploy)+Runtime phase, but fails them
-
- Closed
-