docs: remove outdated pipectl init section from docs-v0.56.x

[A-d-i-t-y]

What this PR does

Removes the outdated "Generating an application config" section from
the docs-v0.56.x command-line-tool page. The pipectl init command
was removed in PR #5958 but the documentation was never updated.

Which issue this fixes

Fixes #6777

Changes

• Removed "Generating an application config (app.pipecd.yaml)" section
• Removed init from the Available Commands help output

Does this PR introduce a user-facing change?

Yes — users will no longer see documentation for a command that does
not exist, preventing confusion.

References

• Related issue: Command-line tool: pipectl CLI docs reference removed pipectl init command, missing migrate and plugin #6750
• Command removed in PR: Remove pipectl init command #5958

[A-d-i-t-y]

Hi @Warashi @khanhtc1202 @eeshaanSA @ffjlabo @rahulshendre

This PR removes the outdated pipectl init documentation from the docs-v0.56.x command-line-tool page. The command was removed in PR #5958 but the docs were never updated, which causes confusion for users following the official v0.56.x docs.

Would appreciate a review when you get a chance. Happy to make any changes if needed!

[Ayushmore1214]

Docs less v1.0.x dont needs to be updated I guess, its not confirmed yet let me ask @rahulshendre what do you think ?

[A-d-i-t-y]

Hi @Ayushmore1214,

Thank you for the review!

Regarding docs-v1.0.x - I checked and the pipectl init section
appears to still be present there as well. I can update that file
in the same PR if needed, or open a separate PR for it.

Please let me know what @rahulshendre suggests and I will update
accordingly. Happy to make any changes!

[rahulshendre]

Docs less v1.0.x dont needs to be updated I guess, its not confirmed yet let me ask @rahulshendre what do you think ?

@Ayushmore1214, docs older than 0.50x don't need to be updated going forward ref-#6729 (review)

Also, there may be a few more related changes needed in the v0.56.x docs, so let's discuss the overall approach with the maintainers in the next community meeting before proceeding.

[A-d-i-t-y]

Thank you for the clarification @rahulshendre and @Ayushmore1214!

Understood - I will wait for the community meeting discussion before
proceeding with any further changes to docs-v0.56.x.

Should I keep this PR open until then, or would you prefer I close
it and re-open after the meeting?

[Ayushmore1214]

@A-d-i-t-y keep it open as we need to discuss things in it as well, you can make it draft pr if you want to

[vedantlavale]

@rahulshendre @Ayushmore1214 I had already raised the issue and opened a supporting PR for this exact same change in the v1.0.x docs last week:

#6750
#6751

Just wanted to point out that there are now duplicate PRs for the same change while the original PR is still open. It would be great if the existing work could be considered first to avoid duplicate efforts and confusion.

[Ayushmore1214]

@A-d-i-t-y plz wait to get issues assigned to yourself first and then go for a PR, discuss your intent in the issue, there is already a PR for this issue #6751 by @vedantlavale so we might have to close this one!!

[Ayushmore1214]

@rahulshendre @Ayushmore1214 I had already raised the issue and opened a supporting PR for this exact same change in the v1.0.x docs last week:

#6750 #6751

Just wanted to point out that there are now duplicate PRs for the same change while the original PR is still open. It would be great if the existing work could be considered first to avoid duplicate efforts and confusion.

thanks for the nudge and clarification we are closing this one