automate
automate copied to clipboard
Adding Grace Period to the license status
:nut_and_bolt: Description: What code changed, and why?
Adding Grace Period to the license status response
:chains: Related Resources
https://chefio.atlassian.net/browse/CHEF-12686
:+1: Definition of Done
Adding Grace Period to the license status response
:athletic_shoe: How to Build and Test the Change
rebuild component/automate-deployment/ rebuild component/automate-gateway/ rebuild component/automate-cli/ rebuild component/license-control-service/
:white_check_mark: Checklist
All PRs must tick these:
- [x] I have read the CONTRIBUTING document.
- [x] All commits signed-off for the Developer Certification of Origin.
With occasional exceptions, all PRs from Progress employees must tick these:
- [x] Is the code clear? (complicated code or lots of comments--subdivide and use well-named methods, meaningful variable names, etc.)
- [x] Consistency checked? (user notifications, user prompts, visual patterns, code patterns, variable names)
- [x] Repeated code blocks eliminated? (adapt and reuse existing components, blocks, functions, etc.)
- [x] Spelling, grammar, typos checked? (at a minimum use
make spellin any component directory) - [x] Code well-formatted? (indents, line breaks, etc. improve rather than hinder readability)
All PRs from Progress employees should tick these if appropriate:
- [ ] Tests added/updated? (all new code needs new tests)
- [ ] Docs added/updated? (all customer-facing changes)
Please add a note next to any checkbox above if you are NOT ticking it.
:camera: Screenshots, if applicable
video link: https://progresssoftware-my.sharepoint.com/:v:/g/personal/swatign_progress_com/ETvj1HPRIJxBmjYyl8n53HYBcHqlO1sqz7GnCSjD3fr9Nw?e=IE2FHn
Quality Gate failed
Failed conditions
2 New issues
2.9% Coverage on New Code (required ≥ 80%)
See analysis details on SonarQube
Catch issues before they fail your Quality Gate with our IDE extension
SonarLint