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

I have added a commands to Export proxy variables for clear understan… #80848

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

Conversation

cainneri
Copy link
Contributor

@cainneri cainneri commented Aug 23, 2024

…ding

I have made PR for adding commands to export proxy variables in the etcd backup process.

Version(s):
4.12+

Issue:
OCPBUGS-33384

Link to docs preview:
https://80848--ocpdocs-pr.netlify.app/openshift-enterprise/latest/backup_and_restore/control_plane_backup_and_restore/backing-up-etcd.html#backing-up-etcd-data_backup-etcd

QE review:

  • QE has approved this change.

@openshift-ci openshift-ci bot added size/S Denotes a PR that changes 10-29 lines, ignoring generated files. needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Aug 23, 2024
Copy link

openshift-ci bot commented Aug 23, 2024

Hi @cainneri. Thanks for your PR.

I'm waiting for a openshift member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@lahinson
Copy link
Contributor

/ok-to-test

@openshift-ci openshift-ci bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Aug 26, 2024
Copy link
Contributor

@lahinson lahinson left a comment

Choose a reason for hiding this comment

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

Hi @cainneri - I edited your proposed text according to the OpenShift doc guidelines.

As per the suggestions, Changes have been made.

Co-authored-by: Laura Hinson <lahinson@redhat.com>
@cainneri
Copy link
Contributor Author

cainneri commented Sep 3, 2024

Hi @lahinson I have made required Changes. Kindly Please review and Let me know if i need to add anything further

@lahinson
Copy link
Contributor

lahinson commented Sep 3, 2024

Hi @cainneri - As you can see in the docs preview, the formatting is still not quite right:

Screenshot 2024-09-03 at 10 00 51 AM

If you incorporate the rest of my suggested changes, I believe that should fix the formatting issues.

cainneri and others added 10 commits September 3, 2024 20:28
I have made the suggested change

Co-authored-by: Laura Hinson <lahinson@redhat.com>
I have made the suggested changes

Co-authored-by: Laura Hinson <lahinson@redhat.com>
Co-authored-by: Laura Hinson <lahinson@redhat.com>
Co-authored-by: Laura Hinson <lahinson@redhat.com>
Co-authored-by: Laura Hinson <lahinson@redhat.com>
Co-authored-by: Laura Hinson <lahinson@redhat.com>
Co-authored-by: Laura Hinson <lahinson@redhat.com>
Co-authored-by: Laura Hinson <lahinson@redhat.com>
Co-authored-by: Laura Hinson <lahinson@redhat.com>
Co-authored-by: Laura Hinson <lahinson@redhat.com>
@cainneri
Copy link
Contributor Author

cainneri commented Sep 3, 2024

hi @lahinson I have made required Changes. Kindly Please review and Let me know if i need to add anything further

Copy link
Contributor

@lahinson lahinson left a comment

Choose a reason for hiding this comment

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

@cainneri In the preview, I see one very small formatting issue that needs to be fixed. Hopefully, it should be easy to fix. Thank you!

. If the cluster-wide proxy is enabled, ensure that you exported the `NO_PROXY`, `HTTP_PROXY`, and `HTTPS_PROXY` environment variables.
+
.. To export the `HTTP_PROXY`, `HTTPS_PROXY`, and `NO_PROXY` environment variables, run the following commands:

Copy link
Contributor

Choose a reason for hiding this comment

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

I think the formatting issues will be resolved if you remove this line. For example, the text should look like this:

.. To export the `HTTP_PROXY`, `HTTPS_PROXY`, and `NO_PROXY` environment variables, run the following commands:
+
[source,terminal]
----
$ export HTTP_PROXY=http://<your_proxy.example.com>:8080
----
+
[source,terminal]
----
$ export HTTPS_PROXY=https://<your_proxy.example.com>:8080
----
+
[source,terminal]
----
$ export NO_PROXY=<example.com>
----

@lahinson lahinson added the peer-review-done Signifies that the peer review team has reviewed this PR label Sep 4, 2024
@lahinson
Copy link
Contributor

lahinson commented Sep 4, 2024

Hi @cainneri - The formatting looks good now. I will add this to the queue for merge review. I noticed that you need to squash your commits. You will need to use the command line to do that. You can find the instructions here: https://docs.google.com/document/d/1fLMpK4bqthtFlCwA36yeo2cI-pExFpX76VMnSi_In6Q/edit#bookmark=id.9bn6glcn7tle

@lahinson lahinson added the merge-review-needed Signifies that the merge review team needs to review this PR label Sep 4, 2024
@jeana-redhat jeana-redhat added the merge-review-in-progress Signifies that the merge review team is reviewing this PR label Sep 4, 2024
Copy link
Contributor

@jeana-redhat jeana-redhat left a comment

Choose a reason for hiding this comment

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

@cainneri thanks for this great addition to the docs!

As Laura mentioned, this needs to be squashed to a single commit before we can merge it. I have also left a small formatting fix on the file, but it should be straightforward to just copy and paste into the file.

Please copy over the suggested format fix, and then squash this to a single commit. We can help you get it merged from that point 🤓

/remove-label merge-review-in-progress
/remove-label merge-review-needed

@openshift-ci openshift-ci bot removed merge-review-in-progress Signifies that the merge review team is reviewing this PR merge-review-needed Signifies that the merge review team needs to review this PR labels Sep 4, 2024
Co-authored-by: Jeana Routh <61474374+jeana-redhat@users.noreply.github.com>
Copy link

openshift-ci bot commented Sep 5, 2024

@cainneri: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@bergerhoffer
Copy link
Contributor

The branch/enterprise-4.18 label has been added to this PR.

This is because your PR targets the main branch and is labeled for enterprise-4.17. And any PR going into main must also target the latest version branch (enterprise-4.18).

If the update in your PR does NOT apply to version 4.18 onward, please re-target this PR to go directly into the appropriate version branch or branches (enterprise-4.x) instead of main.

@openshift-merge-robot openshift-merge-robot added the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Oct 14, 2024
@openshift-merge-robot
Copy link

PR needs rebase.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@openshift-bot
Copy link

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

@openshift-ci openshift-ci bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 14, 2025
@openshift-bot
Copy link

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

@openshift-ci openshift-ci bot added lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. and removed lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. labels Feb 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch/enterprise-4.12 branch/enterprise-4.13 branch/enterprise-4.14 branch/enterprise-4.15 branch/enterprise-4.16 branch/enterprise-4.17 branch/enterprise-4.18 lifecycle/rotten Denotes an issue or PR that has aged beyond stale and will be auto-closed. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. peer-review-done Signifies that the peer review team has reviewed this PR size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants