-
Notifications
You must be signed in to change notification settings - Fork 148
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix branding template body path parsing issue #943
Conversation
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## master #943 +/- ##
==========================================
- Coverage 84.33% 84.32% -0.01%
==========================================
Files 116 116
Lines 3791 3802 +11
Branches 743 745 +2
==========================================
+ Hits 3197 3206 +9
- Misses 328 329 +1
- Partials 266 267 +1 ☔ View full report in Codecov by Sentry. |
Quick question, our pipeline is failing with this error |
Hi, @vasantteja I have tested for tenant.yaml:
Windows path on yaml:
Same test has been done for |
Thanks for the update. Appreciate the help. |
Hi @kushalshit27, I noticed that another PR related to this issue was merged in version 7.24.1. I used it to run our pipeline, but it failed with the same error mentioned above. I assume our issue will not be resolved until this PR is merged. Do you have any idea when this PR will be merged? |
f2a934d
to
84059b8
Compare
DXCDT-689:nomalizedYAMLPath util added to handle branding template path DXCDT-689: rename variable to be more descriptive DXCDT-689: Fix branding directory handler DXCDT-689: rename variable to be more descriptive DXCDT-689: rename variable to be more descriptive DXCDT-689: rename variable to be more descriptive DXCDT-689: Fix branding directory handler DXCDT-689: Fix branding directory handler
fb251bb
to
1a66515
Compare
@vasantteja planning to release today! |
DXCDT-689: Fix branding template body path parsing issue Issue The branding location changes is a breaking change #941
🔧 Changes
📚 References
🔬 Testing
Testing has been done considering different path for POSIX and Windows.
For tenant.yaml:
POSIX path on yaml:
Windows path on yaml:
Same test has been done for
json(directory)
export/import.📝 Checklist