Skip to content
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

docs: working with stages documentation #2608

Open
wants to merge 5 commits into
base: main
Choose a base branch
from

Conversation

fykaa
Copy link
Contributor

@fykaa fykaa commented Sep 30, 2024

fixes #2339

image

@fykaa fykaa self-assigned this Sep 30, 2024
@fykaa fykaa requested review from a team as code owners September 30, 2024 12:05
Copy link

netlify bot commented Sep 30, 2024

Deploy Preview for docs-kargo-akuity-io ready!

Name Link
🔨 Latest commit 2410cc3
🔍 Latest deploy log https://app.netlify.com/sites/docs-kargo-akuity-io/deploys/66fa97cbc33f3f0008a38c03
😎 Deploy Preview https://deploy-preview-2608.kargo.akuity.io
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link

codecov bot commented Sep 30, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 51.40%. Comparing base (17a58cf) to head (8c63c12).
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #2608      +/-   ##
==========================================
+ Coverage   51.35%   51.40%   +0.04%     
==========================================
  Files         287      288       +1     
  Lines       26022    26100      +78     
==========================================
+ Hits        13363    13416      +53     
- Misses      11938    11959      +21     
- Partials      721      725       +4     

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

@krancour
Copy link
Member

krancour commented Oct 8, 2024

This feels misplaced. Scanning the rest of the concepts doc, there are no other occurrences of demonstrating CLI commands. I think we should keep this page focused on concepts and how they map to CRDs. This raises the question of where this documentation of kargo verify belongs, and I would suggest it calls for the creation of a "Working with Stages" guide similar to the "Working with Freight" guide. This will hopefully also help advance us farther toward the longer term goal of organizing the doc tree to have separate branches for user topics and operator topics.

@krancour krancour removed this from the v1.0.0 milestone Oct 11, 2024
@krancour krancour added this to the Live Docs milestone Oct 24, 2024
Copy link

netlify bot commented Oct 28, 2024

Deploy Preview for docs-kargo-io ready!

Name Link
🔨 Latest commit 8c63c12
🔍 Latest deploy log https://app.netlify.com/sites/docs-kargo-io/deploys/6769612c030a6b00089eff00
😎 Deploy Preview https://deploy-preview-2608.docs.kargo.io
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

@fykaa fykaa requested a review from krancour November 5, 2024 10:24
@fykaa fykaa force-pushed the docs-kargo-verify-command branch from f28e5bd to b012ab9 Compare November 13, 2024 12:36
kargo verify stage --project=<project-name> <stage-name>
```

2. To stop an ongoing verification process, use:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is awkward. It's being presented as:

Step 1: Start verification
Step 2: Abort it

Those feel like two different things, rather than elements of the same sequence.

This also differs from the UI-centric instructions above, which didn't talk about aborting a verification, but went from starting one to showing how you can see which Stages a piece of Freight has been verified in.

We should try to keep things consistent and have the UI and CLI tabs cover the same things in the same order.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree, I’ll updated the 'Reverifying a Stage’s Current Freight' section to align the UI and CLI instructions to only include a subtle guidance on aborting verification, and a CLI command to check verified stages. It should be now consistent with the UI tab

Signed-off-by: Kent Rancourt <[email protected]>

Apply suggestions from code review

Signed-off-by: Kent Rancourt <[email protected]>

Apply suggestions from code review

Signed-off-by: Kent Rancourt <[email protected]>

Apply suggestions from code review

Signed-off-by: Kent Rancourt <[email protected]>
@fykaa fykaa force-pushed the docs-kargo-verify-command branch 2 times, most recently from 907eefb to cbf092b Compare December 23, 2024 11:41
Signed-off-by: Faeka Ansari <[email protected]>
@fykaa fykaa force-pushed the docs-kargo-verify-command branch from cbf092b to 8c63c12 Compare December 23, 2024 13:10

![verify-stage](../../static/img/reverify-freight.png)

If you want to stop the verification process mid-way, you can click the <Hlt>Abort Verification</Hlt> button next to the Reverify option.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
If you want to stop the verification process mid-way, you can click the <Hlt>Abort Verification</Hlt> button next to the Reverify option.
:::note
If you wish to stop the in-progress verification, you can click <Hlt>Abort Verification</Hlt>.
:::

Comment on lines +579 to +581
:::note
For detailed instructions on promoting a `Stage`, refer to the Working with Promotions page.
:::
Copy link
Member

@krancour krancour Dec 23, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this little bit here is going to be much too-easily overlooked.

I think I would carve out a separate ###-level section under Interacting with Stages -- fairly high up as well -- probably right after the section with instructions for creating a stage.

The section doesn't really need much more detail than what you've got in this note box here.

The point is that I just want this reference to the Promotion docs page in a more prominent place.

Nit on "promoting": Promotions require a pair of arguments. "Promoting a Stage" therefore doesn't make sense. So when you move this, please also consider rewording to be inclusive of both equally important arguments. Something like: "For detailed instructions for promoting Freight to a Stage...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

docs: need to document kargo verify command
2 participants