feat(cli): adding gpg examples (#15690)

[gaurangkudale]

adding logout examples for improvement #15690

Checklist:

• Either (a) I've created an enhancement proposal and discussed it with the community, (b) this is a bug fix, or (c) this does not need to be in the release notes.
• The title of the PR states what changed and the related issues number (used for the release note).
• The title of the PR conforms to the Toolchain Guide
• I've included "Closes [ISSUE #]" or "Fixes [ISSUE #]" in the description to automatically close the associated issue.
• I've updated both the CLI and UI to expose my feature, or I plan to submit a second PR with them.
• Does this PR require documentation updates?
• I've updated documentation as required by this PR.
• Optional. My organization is added to USERS.md.
• I have signed off all my commits as required by DCO
• I have written unit and/or e2e tests for my change. PRs without these are unlikely to be merged.
• My build is green (troubleshooting builds).
• My new feature complies with the feature status guidelines.
• I have added a brief description of why this PR is necessary and/or what this PR solves.

[codecov]

Codecov Report

Attention: 12 lines in your changes are missing coverage. Please review.

Comparison is base (4f8c147) 49.56% compared to head (1446fc0) 49.54%.
Report is 3 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master   #15844      +/-   ##
==========================================
- Coverage   49.56%   49.54%   -0.02%     
==========================================
  Files         269      269              
  Lines       46668    46680      +12     
==========================================
- Hits        23131    23128       -3     
- Misses      21263    21277      +14     
- Partials     2274     2275       +1     

Files	Coverage Δ
cmd/argocd/commands/gpg.go	0.00% <0.00%> (ø)

... and 2 files with indirect coverage changes

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

[gaurangkudale]

I am not able to figure out why this check is failing https://github.com/argoproj/argo-cd/actions/runs/6430691978/job/17462132638?pr=15844
Can anyone please clear this for me?

[blakepettersson]

Can anyone please clear this for me?

You should be able to either run make clidocsgen or alternatively you can modify docs/user-guide/commands/argocd_gpg_list.md, docs/user-guide/commands/argocd_gpg_rm.md etc to match the output in the failing task.

[gaurangkudale]

Can anyone please clear this for me?

You should be able to either run make clidocsgen or alternatively you can modify docs/user-guide/commands/argocd_gpg_list.md, docs/user-guide/commands/argocd_gpg_rm.md etc to match the output in the failing task.

Thanks @blakepettersson For clearing this for me
I ran make clidocsgen cmd lets wait for check to pass

[crenshaw-dev]

Could you either un-indent the string or use the templates.Examples function to correct indentation?

[gaurangkudale]

Yes I have done the changes for all .md files

[gaurangkudale]

If I run make clidocsgen command then it is adding the un-indentation to the string
So is it necessary to run make clidocsgen in this case?

[crenshaw-dev]

You have to remove the indentation in the .go files and then run make clidocsgen.

So,

		Example: `
# Remove a GPG public key from the server's key using its key ID 
argocd gpg rm <KEYID>
		`,

Looks weird, but it gets the job done :-)

[gaurangkudale]

Got it! Thanks for the suggestions
I hope all checks will pass now

[crenshaw-dev]

Almost there! Can you un-indent the examples for all 4 commands?

[gaurangkudale]

Almost there! Can you un-indent the examples for all 4 commands?

Is it okay if I do it manually because whenever I use make clidocsgen it is adding the spaces at the start of .md file

[gaurangkudale]

@crenshaw-dev If I manually run maken clidocsgen cmd then Integration tests / Check changes to generated code (pull_request) check is failing
Trying to figure out the way to make it work

[ishitasequeira]

@gaurangkudale please resolve the merge conflicts

[ishitasequeira]

@gaurangkudale would you mind resolving conflicts?