Browse Source

cleanup

pull/1/head
Nicolas Massé 6 years ago
parent
commit
5df2855e47
  1. 5
      lab-instructions/config.toml
  2. 2
      lab-instructions/content/automate/exercise-git.md

5
lab-instructions/config.toml

@ -17,9 +17,6 @@ themeVariant = "red"
# you can comment out the editURL parameter once the workshop has been proofread
editURL = "https://github.com/nmasse-itix/microcks-workshop/edit/master/lab-instructions/content/"
# OpenShift Console URL (scheme, hostname and port)
openshift_console_url="https://openshift.itix.fr:8443"
# Microcks installation (scheme, hostname and port)
microcks_url="https://microcks.app.itix.fr"
@ -31,7 +28,7 @@ microcks_client_secret="30975a1b-eada-4379-89e8-99c8619462c6"
apicurio_studio_url="https://apicurio-studio.app.itix.fr"
# On-site GitHub installation (scheme, hostname and port)
github_url="https://github.com/"
github_url="https://github.com"
# Petstore API implementation, deployed twice as explained in api-backend/nodejs/README.md
petstore_api="http://petstore-api.app.itix.fr"

2
lab-instructions/content/automate/exercise-git.md

@ -8,7 +8,7 @@ weight: 1
Because ACME adheres to the Infrastructure-as-Code and API-Management-as-Code principles, everything needs to be versioned in a GIT repository.
In this exercise, you will create a GIT repository and publish your API contract.
- Go to your [favourite GIT provider]({{< param github_url >}})
- Go to your [favourite GIT provider]({{< param github_url >}}/new)
- Create a repository named `petstore-api`
- **Hint:** You can initialize it with a README and a license file when proposed by your GIT provider
- Open the [APICurio Studio]({{< param apicurio_studio_url >}}/apis)

Loading…
Cancel
Save