-
Notifications
You must be signed in to change notification settings - Fork 59
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: Expose cluster information for Workflow Executions #78
Conversation
Codecov Report
@@ Coverage Diff @@
## master #78 +/- ##
==========================================
+ Coverage 62.88% 63.06% +0.17%
==========================================
Files 361 363 +2
Lines 5647 5685 +38
Branches 837 840 +3
==========================================
+ Hits 3551 3585 +34
- Misses 2096 2100 +4
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some minor suggestions inline, but LGTM 👍
src/components/Executions/ExecutionDetails/ExecutionMetadata.tsx
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍
## [0.7.1](http://github.com/lyft/flyteconsole/compare/v0.7.0...v0.7.1) (2020-07-01) ### Bug Fixes * Expose cluster information for Workflow Executions ([#78](http://github.com/lyft/flyteconsole/issues/78)) ([d43a1e3](http://github.com/lyft/flyteconsole/commit/d43a1e393ef7b0651f9774460e3d7166a3b57f17))
🎉 This PR is included in version 0.7.1 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
The primary goal was to expose a piece of metadata that is useful in debugging. But since the portion of the page where we show execution details is already pretty crowded, I decided to implement a restyling that would be part of some upcoming design changes for the execution details page. This gave me more room to add the extra piece of information
spec.metadata.systemMetadata.executionClusterName
property will just show "(unknown)"Before:
After:
Expansions: