openshift-docs
openshift-docs copied to clipboard
OCPBUGS-32397: Add links to FlowCollector API Reference in the NetObserv Configuration guide
Version(s):
4.12+ Issue:
https://issues.redhat.com/browse/OCPBUGS-32397 Link to docs preview:
https://78138--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/network_observability/configuring-operator.html QE review:
- QE not required. This is just making more prominent links to existing API documentation that is already in the Network Observability docs. I guess, a QE ACK would be nice but it isn't anything technically requiring hard review.
Additional information:
@skrthomas: This pull request references Jira Issue OCPBUGS-32397, which is invalid:
- expected the bug to target the "4.17.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:
Version(s):
4.12+ Issue:
https://issues.redhat.com/browse/OCPBUGS-32397 Link to docs preview:
QE review:
- [ ] QE has approved this change.
Additional information:
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.
🤖 Wed Jul 10 19:50:44 - Prow CI generated the docs preview:
https://78138--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/network_observability/configuring-operator.html https://78138--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/network_observability/flowcollector-api.html https://78138--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/network_observability/json-flows-format-reference.html
@skrthomas: This pull request references Jira Issue OCPBUGS-32397, which is invalid:
- expected the bug to target the "4.17.0" version, but no target version was set
- expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is MODIFIED instead
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.
In response to this:
Version(s):
4.12+ Issue:
https://issues.redhat.com/browse/OCPBUGS-32397 Link to docs preview:
https://78138--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/network_observability/configuring-operator.html QE review:
- [ ] QE has approved this change.
Additional information:
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.
@skrthomas: This pull request references Jira Issue OCPBUGS-32397, which is invalid:
- expected the bug to target the "4.17.0" version, but no target version was set
- expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is MODIFIED instead
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:
Version(s):
4.12+ Issue:
https://issues.redhat.com/browse/OCPBUGS-32397 Link to docs preview:
https://78138--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/network_observability/configuring-operator.html QE review:
- QE not required. This is just making more prominent links to existing API documentation that is already in the Network Observability docs.
Additional information:
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.
@skrthomas: This pull request references Jira Issue OCPBUGS-32397, which is invalid:
- expected the bug to target the "4.17.0" version, but no target version was set
- expected the bug to be in one of the following states: NEW, ASSIGNED, POST, but it is ON_QA instead
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.
In response to this:
Version(s):
4.12+ Issue:
https://issues.redhat.com/browse/OCPBUGS-32397 Link to docs preview:
https://78138--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/network_observability/configuring-operator.html QE review:
- QE not required. This is just making more prominent links to existing API documentation that is already in the Network Observability docs. I guess, a QE ACK would be nice but it isn't anything technically requiring hard review.
Additional information:
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.
@skrthomas: 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.
@skrthomas: Jira Issue OCPBUGS-32397 is in an unrecognized state (Release Pending) and will not be moved to the MODIFIED state.
In response to this:
Version(s):
4.12+ Issue:
https://issues.redhat.com/browse/OCPBUGS-32397 Link to docs preview:
https://78138--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/network_observability/configuring-operator.html QE review:
- QE not required. This is just making more prominent links to existing API documentation that is already in the Network Observability docs. I guess, a QE ACK would be nice but it isn't anything technically requiring hard review.
Additional information:
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.
/cherrypick enterprise-4.12
/cherrypick enterprise-4.13
/cherrypick enterprise-4.14
/cherrypick enterprise-4.15
/cherrypick enterprise-4.16
/cherrypick enterprise-4.17
@skrthomas: new pull request created: #78751
In response to this:
/cherrypick enterprise-4.12
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.
@skrthomas: new pull request created: #78752
In response to this:
/cherrypick enterprise-4.13
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.
@skrthomas: new pull request created: #78753
In response to this:
/cherrypick enterprise-4.14
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.
@skrthomas: new pull request created: #78754
In response to this:
/cherrypick enterprise-4.15
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.
@skrthomas: new pull request created: #78755
In response to this:
/cherrypick enterprise-4.16
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.
@skrthomas: new pull request created: #78756
In response to this:
/cherrypick enterprise-4.17
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.