-
Story
-
Resolution: Unresolved
-
Critical
-
None
-
None
-
Product / Portfolio Work
-
3
-
False
-
-
False
-
Not Selected
-
-
-
Workloads - Train 35 - 2
-
None
Value Statement
Tracking work for https://issues.redhat.com/browse/ACM-24872 . The linter should detect variables that are declared and not used, or variables that are defined in one scope and referenced in the wrong template scope (eg hub vs managed).
The linter should also detect invalid syntax using a variable inside a dot operator, eg {{ $vm.annotations.$annotationName }}
Definition of Done for Engineering Story Owner (Checklist)
- ...
Development Complete
- The code is complete.
- Functionality is working.
- Any required downstream Docker file changes are made.
Tests Automated
- [ ] Unit/function tests have been automated and incorporated into the build.
- [ ] 100% automated unit/function test coverage for new or changed APIs.
Secure Design
- [ ] Security has been assessed and incorporated into your threat model.
Multidisciplinary Teams Readiness
- [ ] Create an informative documentation issue using the Customer Portal Doc template that you can access from The Playbook, and ensure doc acceptance criteria is met.
- Call out this sentence as it's own action:
- [ ] Link the development issue to the doc issue.
Support Readiness
- [ ] The must-gather script has been updated.