ADD userguide/managingApp/deployment-trace

[rahulshendre]

What this PR does:

File by file commit from the bigger PR - #6345

Adds the “Deployment trace” page under User Guide → Managing Application.

Related to #6395

Why we need it:

Which issue(s) this PR fixes:

Fixes #

Does this PR introduce a user-facing change?:

• How are users affected by this change:
• Is this breaking change:
• How to migrate (if breaking change):

[eeshaanSA]

Hey @rahulshendre, I commited my changes, but I cant see them here. Can you see them? Here is the link to the changes I made: rahulshendre@ba4c012

Weird.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 37.07%. Comparing base (ebc267c) to head (41cac5e).
⚠️ Report is 14 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #6413      +/-   ##
==========================================
+ Coverage   28.87%   37.07%   +8.20%     
==========================================
  Files         560       75     -485     
  Lines       59955     6500   -53455     
==========================================
- Hits        17313     2410   -14903     
+ Misses      41321     3952   -37369     
+ Partials     1321      138    -1183     

Flag	Coverage Δ
.	?
.-pkg-app-pipedv1-plugin-analysis	32.64% <ø> (ø)
.-pkg-app-pipedv1-plugin-kubernetes	?
.-pkg-app-pipedv1-plugin-kubernetes_multicluster	?
.-pkg-app-pipedv1-plugin-scriptrun	54.83% <ø> (ø)
.-pkg-app-pipedv1-plugin-terraform	38.65% <ø> (ø)
.-pkg-app-pipedv1-plugin-wait	33.92% <ø> (ø)
.-pkg-app-pipedv1-plugin-waitapproval	52.71% <ø> (ø)
.-pkg-plugin-sdk	50.34% <ø> (ø)
.-tool-actions-gh-release	19.23% <ø> (ø)
.-tool-actions-plan-preview	25.51% <ø> (ø)
.-tool-codegen-protoc-gen-auth	0.00% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[rahulshendre]

Hey @rahulshendre, I commited my changes, but I cant see them here. Can you see them? Here is the link to the changes I made: rahulshendre@ba4c012

@eeshaanSA, I can see the changes.
LGTM, thanks : )

[khanhtc1202]

@rahulshendre @eeshaanSA this page is Deployment Trace while the title and description is Deployment Chain? 👀

[rahulshendre]

Thanks for pointing this out @khanhtc1202.
The name slipped in from the initial checklist we prepared.

In v0, Deployment Chain refers to the postSync orchestration feature.
In v1, this page describes a feature that maps code commits to the deployments they trigger.

Using “Deployment Trace” seemed appropriate here, what do you think?

[eeshaanSA]

Hey, sorry for missing it. The title and the body needs to be changed.

The files changed, however, only add docs for Deployment Trace.

@rahulshendre please keep a look out for such mistakes, I do miss it sometimes. 😃

[rahulshendre]

Thanks @eeshaanSA, I have updated the PR title and description to Deployment Trace.
Will be more careful going forward : )