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

OCPBUGS-36797: Revisit links to upstream docs in API #226

Merged

Conversation

alebedev87
Copy link
Contributor

@alebedev87 alebedev87 commented Aug 28, 2024

  • Removed links that don't add value and may mislead users (AWS, Infoblox: secret format).
  • Pinned remaining links to specific commits and anchored them to relevant chapters.

@openshift-ci-robot openshift-ci-robot added jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 28, 2024
@openshift-ci-robot
Copy link

@alebedev87: This pull request references Jira Issue OCPBUGS-36797, which is invalid:

  • expected the bug to target the "4.18.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

  • Removed links that don't add value and may mislead users.
  • Pinned remaining links to specific commits and anchored them to relevant chapters.

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested review from miheer and rfredette August 28, 2024 21:41
@alebedev87
Copy link
Contributor Author

/jira refresh

@openshift-ci-robot openshift-ci-robot added jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. and removed jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Aug 28, 2024
@openshift-ci-robot
Copy link

@alebedev87: This pull request references Jira Issue OCPBUGS-36797, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.18.0) matches configured target version for branch (4.18.0)
  • bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @melvinjoseph86

In response to this:

/jira refresh

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 openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot requested a review from melvinjoseph86 August 28, 2024 21:42
@melvinjoseph86
Copy link

As this is doc link removal, QE will verify this after the merger....

@alebedev87
Copy link
Contributor Author

/assign @Miciah

@openshift-ci-robot
Copy link

@alebedev87: This pull request references Jira Issue OCPBUGS-36797, which is valid.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target version (4.18.0) matches configured target version for branch (4.18.0)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @melvinjoseph86

In response to this:

  • Removed links that don't add value and may mislead users (AWS, Infoblox: secret format).
  • Pinned remaining links to specific commits and anchored them to relevant chapters.

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 openshift-eng/jira-lifecycle-plugin repository.

@@ -304,7 +300,7 @@ type ExternalDNSAzureProviderOptions struct {
// }
//
// See
// https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/azure.md
// https://github.com/kubernetes-sigs/external-dns/blob/226dbb931f7a2019810b3703aec096c4ea4f40ea/docs/tutorials/azure.md#configuration-file
Copy link
Contributor

Choose a reason for hiding this comment

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

This is fine for now, but I hope in the future we will have some product documentation that we can reference instead.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

My goal was to show which fields can be put into the config. The previous link was a shot in the dark, this change makes the link at least useful. Btw, the config content is kinda opaque for the operator as we don't validate or enforce anything for the moment. But I agree the ultimate goal is to have this in the OCP docs.

Copy link
Contributor Author

@alebedev87 alebedev87 Oct 3, 2024

Choose a reason for hiding this comment

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

@jmanthei : Can you help us with adding of the Azure config file for EzternalDNS' Azure provider to the docs?

UPD: AWS, GCP and Infoblox would need to be there too.

Copy link

Choose a reason for hiding this comment

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

@alebedev87 I'm happy to help- do you have links to existing config files for these that I can glean information from? How soon does this need to be done?

Copy link
Contributor Author

@alebedev87 alebedev87 Oct 3, 2024

Choose a reason for hiding this comment

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

@jmanthei: We can take the upstream links as example. For instance this one from the PR for Azure.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

How soon does this need to be done?

It's not urgent.

Comment on lines 327 to 329
// See
// https://github.com/kubernetes-sigs/external-dns/blob/master/docs/tutorials/bluecat.md
// https://github.com/kubernetes-sigs/external-dns/blob/226dbb931f7a2019810b3703aec096c4ea4f40ea/docs/tutorials/bluecat.md#using-json-configuration-file
// for more information on the necessary configuration values and how to obtain them.
Copy link
Contributor

Choose a reason for hiding this comment

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

The linked documentation just seems to say which fields are required and which are not, but not how to obtain them. I think this change is fine since the goal is just to fix the link, but as I mentioned in my other comment, it would be good in the future to link to product documentation instead.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Right, this one was really for consistency (with Azure). Btw BlueCat is going away so we don't need to bother about it.

@Miciah
Copy link
Contributor

Miciah commented Oct 3, 2024

Thanks!
/approve
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 3, 2024
@alebedev87
Copy link
Contributor Author

/approve

Wake up, Neo ...

Copy link
Contributor

openshift-ci bot commented Oct 3, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: alebedev87, Miciah

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 3, 2024
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 3be5a66 and 2 for PR HEAD dafa06e in total

- Removed links that don't add value and may mislead users.
- Pinned remaining links to specific commits and anchored them to relevant chapters.
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 3be5a66 and 2 for PR HEAD dafa06e in total

@alebedev87
Copy link
Contributor Author

/retest-required

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 3be5a66 and 2 for PR HEAD dafa06e in total

@alebedev87 alebedev87 force-pushed the infoblox-remove-upstream-doc branch from dafa06e to dd227ae Compare October 3, 2024 22:19
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Oct 3, 2024
@alebedev87
Copy link
Contributor Author

/test e2e-gcp-operator

Synchronizes the File-Based Catalog (FBC) with infrastructure annotations
from the latest bundle. This update resolves `make verify` target failures
by regenerating the catalog via `make catalog`.
@alebedev87 alebedev87 force-pushed the infoblox-remove-upstream-doc branch from dd227ae to af77cf2 Compare October 4, 2024 08:35
@alebedev87
Copy link
Contributor Author

/test e2e-aws-shared-vpc-phz-operator

Copy link
Contributor

openshift-ci bot commented Oct 4, 2024

@alebedev87: 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.

@Miciah
Copy link
Contributor

Miciah commented Oct 4, 2024

Thanks!
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 4, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit 663a245 into openshift:main Oct 4, 2024
10 checks passed
@openshift-ci-robot
Copy link

@alebedev87: Jira Issue OCPBUGS-36797: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-36797 has been moved to the MODIFIED state.

In response to this:

  • Removed links that don't add value and may mislead users (AWS, Infoblox: secret format).
  • Pinned remaining links to specific commits and anchored them to relevant chapters.

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 openshift-eng/jira-lifecycle-plugin repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/severity-low Referenced Jira bug's severity is low for the branch this PR is targeting. jira/valid-bug Indicates that a referenced Jira bug is valid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants