Skip to content

Conversation

@dkwon17
Copy link
Contributor

@dkwon17 dkwon17 commented Jan 20, 2025

What does this pull request change?

I've updated some content on the security best practices section: https://eclipse.dev/che/docs/stable/overview/security-best-practices/

What issues does this pull request fix or reference?

Part of verification: https://issues.redhat.com/browse/CRW-7851

Specify the version of the product this pull request applies to

DS 3.18 / Che 7.95

Pull Request checklist

The author and the reviewers validate the content of this pull request with the following checklist, in addition to the automated tests.

  • Any procedure:
    • Successfully tested.
  • Any page or link rename:
    • The page contains a redirection for the previous URL.
    • Propagate the URL change in:
  • Builds on Eclipse Che hosted by Red Hat.
  • the Validate language on files added or modified step reports no vale warnings.

@dkwon17 dkwon17 requested review from a team and deerskindoll as code owners January 20, 2025 15:23
@dkwon17 dkwon17 requested a review from svor January 20, 2025 15:23
@github-actions
Copy link

github-actions bot commented Jan 20, 2025

🎊 Navigate the preview: https://679c1727856509a2ae9a8491--eclipse-che-docs-pr.netlify.app 🎊

@github-actions
Copy link

github-actions bot commented Jan 20, 2025

Click here to review and test in web IDE: Contribute

where cluster administrators control provisioning for each user
and can explicitly configure various settings including resource limits and quotas.
Learn more about project provisioning in the link:https://eclipse.dev/che/docs/stable/administration-guide/mounting-a-secret-as-a-file-or-an-environment-variable-into-a-container/#mounting-a-secret-or-a-configmap-as-an-environment-variable-into-a-container[product documentation].
Learn more about project provisioning in the xref:administration-guide:provisioning-namespaces-in-advance.adoc[product documentation].
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 noticed that the current link was incorrect. I've updated it to the correct link, and also, I've used xref: instead of link:

Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
Learn more about project provisioning in the xref:administration-guide:provisioning-namespaces-in-advance.adoc[product documentation].
Learn more about project provisioning in the xref:provisioning-namespaces-in-advance.adoc[].

Copy link
Contributor Author

Choose a reason for hiding this comment

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

If I apply this change right now, the link does not work, probably because the security best practices doc is not in the administration guide:
image

Can/should we move the security best practices doc to the administration guide?

Copy link
Contributor

Choose a reason for hiding this comment

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

I see what's happening with the xref (was too focused on the formatting). I don't mind the current set up with the security best practices doc being a standalone but moving it to admin guide would solve the issue I'm currently having with getting it to display properly in downstream docs.

Copy link
Contributor

Choose a reason for hiding this comment

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

@ibuziuk is it ok if I move the security best practices doc to the admin guide?

Copy link
Contributor

@deerskindoll deerskindoll left a comment

Choose a reason for hiding this comment

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

lgtm

@deerskindoll
Copy link
Contributor

hi David, I moved the security practices doc and all of its parts into the admin guide #2860 so please update the xrefs. let me know if you need help with them. the [] part of the xref should be empty, the title of the doc will be displayed automatically.

Signed-off-by: dkwon17 <dakwon@redhat.com>
Signed-off-by: dkwon17 <dakwon@redhat.com>
@dkwon17 dkwon17 force-pushed the security-best-practices branch from 9e1336b to 8b8a55c Compare January 29, 2025 16:54
@dkwon17
Copy link
Contributor Author

dkwon17 commented Jan 29, 2025

@deerskindoll thank you, I've rebased against main and updated this PR so that the [] part of the xref is empty

@dkwon17 dkwon17 merged commit 1899719 into eclipse-che:main Jan 31, 2025
6 checks passed
dkwon17 added a commit to dkwon17/che-docs that referenced this pull request Jan 31, 2025
* fix: Update security best practices doc

Signed-off-by: dkwon17 <dakwon@redhat.com>

* Update xref

Signed-off-by: dkwon17 <dakwon@redhat.com>

---------

Signed-off-by: dkwon17 <dakwon@redhat.com>
dkwon17 added a commit that referenced this pull request Jan 31, 2025
* fix: Update security best practices doc



* Update xref



---------

Signed-off-by: dkwon17 <dakwon@redhat.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants