api,server,ui: add project ID and name to UserDataResponse#8656
Conversation
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## 4.19 #8656 +/- ##
============================================
- Coverage 30.90% 30.90% -0.01%
+ Complexity 34189 34187 -2
============================================
Files 5347 5347
Lines 375566 375570 +4
Branches 54625 54626 +1
============================================
- Hits 116068 116056 -12
- Misses 244236 244250 +14
- Partials 15262 15264 +2
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
|
@blueorangutan package |
|
@weizhouapache a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
|
Packaging result [SF]: ✔️ el7 ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 8664 |
|
@weizhouapache , given the name of your branch is this for 4.19? |
@DaanHoogland |
|
I think a backwards compatible enhancement like this can go into a minor release. |
OK @DaanHoogland |
|
@blueorangutan package |
|
@blueorangutan package |
|
@rohityadavcloud a [SL] Jenkins job has been kicked to build packages. It will be bundled with KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress. |
|
Packaging result [SF]: ✔️ el7 ✔️ el8 ✔️ el9 ✔️ debian ✔️ suse15. SL-JID 8678 |
|
@blueorangutan test |
|
@weizhouapache a [SL] Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
|
@blueorangutan test |
|
@rohityadavcloud a [SL] Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests |
|
[SF] Trillian test result (tid-9430)
|
|
@sureshanaparti , I think we can merge at your will. |
* api,server,ui: add project ID and name to UserDataResponse * Update: add since
Description
This PR fixes #8363
Types of changes
Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale
Bug Severity
Screenshots (if appropriate):
How Has This Been Tested?
How did you try to break this feature and the system with this change?