openshift
OBSDOCS-695:Update Network Observability doc links and topic map posi…
…tion
Version(s):
Issue:
https://issues.redhat.com/browse/OBSDOCS-695 Link to docs preview:
https://73554--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/network_observability/network-observability-operator-release-notes QE review:
- [ ] QE has approved this change.
Additional information:
@skrthomas: This pull request references OBSDOCS-695 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.16.0" version, but no target version was set.
In response to this:
…tion
Version(s):
Issue:
https://issues.redhat.com/browse/OBSDOCS-695 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.
🤖 Fri Mar 29 14:09:34 - Prow CI generated the docs preview: https://73554--ocpdocs-pr.netlify.app
@skrthomas: This pull request references OBSDOCS-695 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.16.0" version, but no target version was set.
In response to this:
…tion
Version(s):
Issue:
https://issues.redhat.com/browse/OBSDOCS-695 Link to docs preview:
https://73554--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/network_observability/network-observability-operator-release-notes 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 OBSDOCS-695 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.16.0" version, but no target version was set.
In response to this:
Version(s):
4.12+ Issue:
https://issues.redhat.com/browse/OBSDOCS-695 Link to docs preview:
https://73554--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/network_observability/network-observability-operator-release-notes 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 OBSDOCS-695 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.16.0" version, but no target version was set.
In response to this:
Version(s):
4.12+ Issue:
https://issues.redhat.com/browse/OBSDOCS-695 Link to docs preview:
https://73554--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/network_observability/network-observability-operator-release-notes QE review:
- QE review not required. This change is part of a broad effort to reorganize Observability documentation under an Observability category. This change has been approved by different levels of PM. See, https://github.com/openshift/openshift-docs/pull/71248 and
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 OBSDOCS-695 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.16.0" version, but no target version was set.
In response to this:
Version(s):
4.12+ Issue:
https://issues.redhat.com/browse/OBSDOCS-695 Link to docs preview:
https://73554--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/network_observability/network-observability-operator-release-notes QE review:
- QE review not required. This change is part of a broad effort to reorganize Observability documentation under an Observability category. This change has been approved by different levels of PM. See related PR, https://github.com/openshift/openshift-docs/pull/71248 and
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 OBSDOCS-695 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.16.0" version, but no target version was set.
In response to this:
Version(s):
4.12+ Issue:
https://issues.redhat.com/browse/OBSDOCS-695 Link to docs preview:
https://73554--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/network_observability/network-observability-operator-release-notes QE review:
- QE review not required. This change is part of a broad effort to reorganize Observability documentation under an Observability category. This change has been approved by different levels of PM. See related PR, https://github.com/openshift/openshift-docs/pull/71248 and
Additional information:
This PR changes the topic map file, turns the assembly directories for
network_observabilitysubdirectories of observability, and updates the affected xrefs.
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 OBSDOCS-695 which is a valid jira issue.
Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the task to target the "4.16.0" version, but no target version was set.
In response to this:
Version(s):
4.12+ Issue:
https://issues.redhat.com/browse/OBSDOCS-695 Link to docs preview:
https://73554--ocpdocs-pr.netlify.app/openshift-enterprise/latest/observability/network_observability/network-observability-operator-release-notes QE review:
- QE review not required. This change is part of a broad effort to reorganize Observability documentation under an Observability category. This change has been approved by different levels of PM. See related PR, https://github.com/openshift/openshift-docs/pull/71248 and
Additional information:
This PR changes the topic map file, turns the assembly directory for
network_observabilityinto a subdirectory ofobservability, and updates the affected xrefs.
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.
cc @kalexand-rh not sure what is going on here and why the build is passing.
Thanks @mramendi. I changed the links in networking/networking-dashboards.adoc and networking/networking-operators-overview.adoc to have a link path: xref:../observability/network_observability. However, in all of my other assembly files, I tried to do xref:../observability/network_observability or ../../observability/network_observability, but I kept getting build errors. When I talked to Joe, he suggested doing ../../network_observability. It didn't break the PR he pulled down, so hopefully I'm going to try that on this PR and see.
@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/test-infra repository. I understand the commands that are listed here.
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
@kelbrown20: new pull request created: #73947
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/test-infra repository.
@kelbrown20: new pull request created: #73948
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/test-infra repository.
@kelbrown20: #73554 failed to apply on top of branch "enterprise-4.14":
Applying: OBSDOCS-695:Update Network Observability doc links and topic map position
.git/rebase-apply/patch:304: trailing whitespace.
* xref:../../observability/network_observability/flowcollector-api.adoc#network-observability-flowcollector-api-specifications_network_observability[Flow Collector API Reference]
warning: 1 line adds whitespace errors.
Using index info to reconstruct a base tree...
M _topic_maps/_topic_map.yml
A networking/networking-dashboards.adoc
M welcome/index.adoc
Falling back to patching base and 3-way merge...
Auto-merging welcome/index.adoc
CONFLICT (content): Merge conflict in welcome/index.adoc
CONFLICT (content): Merge conflict in observability/network_observability/snippets
CONFLICT (content): Merge conflict in observability/network_observability/modules
CONFLICT (content): Merge conflict in observability/network_observability/images
CONFLICT (content): Merge conflict in observability/network_observability/_attributes
CONFLICT (modify/delete): networking/networking-dashboards.adoc deleted in HEAD and modified in OBSDOCS-695:Update Network Observability doc links and topic map position. Version OBSDOCS-695:Update Network Observability doc links and topic map position of networking/networking-dashboards.adoc left in tree.
Removing network_observability/installing-operators.adoc
Auto-merging _topic_maps/_topic_map.yml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 OBSDOCS-695:Update Network Observability doc links and topic map position
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
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/test-infra repository.
@kelbrown20: #73554 failed to apply on top of branch "enterprise-4.13":
Applying: OBSDOCS-695:Update Network Observability doc links and topic map position
.git/rebase-apply/patch:304: trailing whitespace.
* xref:../../observability/network_observability/flowcollector-api.adoc#network-observability-flowcollector-api-specifications_network_observability[Flow Collector API Reference]
warning: 1 line adds whitespace errors.
Using index info to reconstruct a base tree...
M _topic_maps/_topic_map.yml
M network_observability/network-observability-operator-release-notes.adoc
A networking/networking-dashboards.adoc
M observability/index.adoc
M welcome/index.adoc
Falling back to patching base and 3-way merge...
Auto-merging welcome/index.adoc
CONFLICT (content): Merge conflict in welcome/index.adoc
CONFLICT (content): Merge conflict in observability/network_observability/snippets
Auto-merging observability/network_observability/network-observability-operator-release-notes.adoc
CONFLICT (content): Merge conflict in observability/network_observability/network-observability-operator-release-notes.adoc
CONFLICT (content): Merge conflict in observability/network_observability/modules
CONFLICT (content): Merge conflict in observability/network_observability/images
CONFLICT (content): Merge conflict in observability/network_observability/_attributes
Auto-merging observability/index.adoc
CONFLICT (modify/delete): networking/networking-dashboards.adoc deleted in HEAD and modified in OBSDOCS-695:Update Network Observability doc links and topic map position. Version OBSDOCS-695:Update Network Observability doc links and topic map position of networking/networking-dashboards.adoc left in tree.
Removing network_observability/installing-operators.adoc
Auto-merging _topic_maps/_topic_map.yml
CONFLICT (content): Merge conflict in _topic_maps/_topic_map.yml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 OBSDOCS-695:Update Network Observability doc links and topic map position
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
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/test-infra repository.
@kelbrown20: #73554 failed to apply on top of branch "enterprise-4.12":
Applying: OBSDOCS-695:Update Network Observability doc links and topic map position
.git/rebase-apply/patch:304: trailing whitespace.
* xref:../../observability/network_observability/flowcollector-api.adoc#network-observability-flowcollector-api-specifications_network_observability[Flow Collector API Reference]
warning: 1 line adds whitespace errors.
Using index info to reconstruct a base tree...
M _topic_maps/_topic_map.yml
M network_observability/installing-operators.adoc
M network_observability/network-observability-operator-release-notes.adoc
M network_observability/observing-network-traffic.adoc
A networking/networking-dashboards.adoc
M observability/index.adoc
M welcome/index.adoc
Falling back to patching base and 3-way merge...
Auto-merging welcome/index.adoc
CONFLICT (content): Merge conflict in welcome/index.adoc
CONFLICT (content): Merge conflict in observability/network_observability/snippets
Auto-merging observability/network_observability/observing-network-traffic.adoc
CONFLICT (content): Merge conflict in observability/network_observability/observing-network-traffic.adoc
Auto-merging observability/network_observability/network-observability-operator-release-notes.adoc
CONFLICT (content): Merge conflict in observability/network_observability/network-observability-operator-release-notes.adoc
CONFLICT (content): Merge conflict in observability/network_observability/modules
CONFLICT (content): Merge conflict in observability/network_observability/images
CONFLICT (content): Merge conflict in observability/network_observability/_attributes
Auto-merging observability/index.adoc
CONFLICT (modify/delete): networking/networking-dashboards.adoc deleted in HEAD and modified in OBSDOCS-695:Update Network Observability doc links and topic map position. Version OBSDOCS-695:Update Network Observability doc links and topic map position of networking/networking-dashboards.adoc left in tree.
CONFLICT (modify/delete): network_observability/installing-operators.adoc deleted in OBSDOCS-695:Update Network Observability doc links and topic map position and modified in HEAD. Version HEAD of network_observability/installing-operators.adoc left in tree.
Auto-merging _topic_maps/_topic_map.yml
CONFLICT (content): Merge conflict in _topic_maps/_topic_map.yml
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 OBSDOCS-695:Update Network Observability doc links and topic map position
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".
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/test-infra repository.