Add Rendered k8s pod spec tab to ti details view #39141
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
boring-cyborg
bot
added
area:UI
dirrao
reviewed
Apr 20, 2024
|
This is great ! Also maybe a toggle to switch between JSON and YAML would be so cool ( same feature than inside the kubernetes dashboard ) |
raphaelauv
reviewed
Apr 20, 2024
hussein-awala
approved these changes
Apr 21, 2024
bbovenzi
force-pushed
the
react-rendered-k8s
branch
from
93d5e7a to
3689537
Compare
bbovenzi
requested review from
ryanahamilton,
ashb and
pierrejeambrun
as code owners
amoghrajesh
approved these changes
Apr 30, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Show Rendered K8s Pod Spec in react as a new tab on task instance details
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.