actions/importer-labs
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Update valet-configure-lab.md

Browse Source
This commit is contained in:
j-dunham
2022-08-10 14:32:01 -04:00
committed by GitHub
parent 4da2131c5a
commit 0ad5f12309
1 changed files with 24 additions and 7 deletions
Download Patch File Download Diff File Expand all files Collapse all files
gitlab/valet-configure-lab.md
+24 -7
View File
@@ -29,16 +29,33 @@ In this lab, you will use Valet's `configure` command to set up the required sec
4. In the codespace terminal window click back to the `TERMINAL` tab and run `gh valet configure`.
5. Using the down arrow key to highlight `GitLab CI`, press the spacebar to select, then hit enter to accept.
6. Enter your GitHub Username and press enter.
7. Enter the GitHub PAT generated in step 3 and press enter
8. Enter the GitHub PAT generated in step 3 and press enter.
9. Enter the GitHub instance url or hit enter to accept the default, if you are using github.com then the default is the right choice.
10. Enter the GitLab access token from step 2 and press enter.
11. Enter `http://localhost` for the GitLab instance url
7. At the GitHub Container Registry prompty enter the GitHub PAT generated in step 3 and press enter
8. At the GitHub PAT prompt enter the GitHub PAT generated in step 3 and press enter.
9. At the GitHub url prompt enter the GitHub instance url or hit enter to accept the default, if you are using github.com then the default is the right choice.
10. At the GitLab token prompt enter the GitLab access token from step 2 and press enter.
11. At the GitLab url prompt enter `http://localhost` and press enter.
12. If all went well you should see a similar output in your terminal
ADD_IMAGE_HERE
![configure-result](https://user-images.githubusercontent.com/18723510/183984633-cc893ec2-bb60-4c88-812b-55f03adaef1c.png)
## Verify Valet Works
To verify Valet works we are going to run a `dry-run` command. We will go further into details about the `dry-run` command in a later lab, but for now we just want to confirm that Valet runs with no errors.
To verify Valet works we are going to run a `update` and `dry-run` command. We will go further into details about the `dry-run` command in a later lab, but for now we want to get the latest version of Valet and confirm that Valet can perform a dry-run with no errors.
1. In the codespace terminal update Valet by running `gh valet update`
2. In the terminal you should see a confirmation that it logged into the GitHab Container Registry and pulled the latest version.
```
Login Succeeded
latest: Pulling from valet-customers/valet-cli
Digest: sha256:a7d00dee8a37e25da59daeed44b1543f476b00fa2c41c47f48deeaf34a215bbb
Status: Image is up to date for ghcr.io/valet-customers/valet-cli:latest
ghcr.io/valet-customers/valet-cli:latest
```
3. Next, lets run the dry-run commmand in the codespaces terminal, to verify we can talk to GitLab
```
gh valet dry-run gitlab --output-dir ./tmp/dry-run-lab --namespace valet --project basic-pipeline-example
```
4. In the terminal you should see the command was successful, if not it is a good time to practice the configure command again and make sure the access tokens were generated with the correct premissions
![configure-dry-run](https://user-images.githubusercontent.com/18723510/183989794-d51fa29d-b4c0-4074-8402-a55ffcea3a6b.png)
### Next Lab
Dry run the migration of an GitLab pipeline to GitHub Actions ADD_LINK_HERE