Closed devguyio closed 6 months ago
@devguyio: This pull request references RHOAIENG-1910 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 story to target the "4.16.0" version, but no target version was set.
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: devguyio
The full list of commands accepted by this bot can be found here.
The pull request process is described here
@devguyio: This pull request references RHOAIENG-1910 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 story to target the "4.16.0" version, but no target version was set.
@devguyio: This pull request references RHOAIENG-1910 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 story to target the "4.16.0" version, but no target version was set.
I think the other PR should be usable again, so going to try closing this so that I can reopen the other one again.
It seems the other one can't be re-opened because the branch was either force-pushed or recreated while closed. No worries.
@devguyio: This pull request references RHOAIENG-1910 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 story to target the "4.16.0" version, but no target version was set.
@devguyio: This pull request references RHOAIENG-1910 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 story to target the "4.16.0" version, but no target version was set.
@devguyio: This pull request references RHOAIENG-1910 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 story to target the "4.16.0" version, but no target version was set.
/lgtm
/retest
Description
While trying to set up the environment from scratch I realized our documentation has become incoherent and difficult to follow without having a previous understanding of the PoC.
So I reworked the docs to try and reach a more coherent flow of documentation that can also work for both setting up the edge clusters in the cloud or locally using OpenShift Local.
You can view the rendered version on the branch directly.
How Has This Been Tested?
Merge criteria: