when source is created at Github and deployed:

Project already exists! When I delete project by hand, deployment continues, but project is not owed by the user! In my case I use evals02.

would be nice to have a way to skip this step - no repository created in Github, use a default repository.

When going through the 1A walkthrough, I noticed that there were some warnings when we do 2.1, step 4.

1. Unable to determine the scheme to use: OpenAPI specification does not provide a `schemes' definition and the specification was uploaded so the originating URL is lost.
2. Operation PUT /api/fruits/{id} does not provide a response schema for code 201
3. Operation DELETE /api/fruits/{id} does not provide a response schema for code 204

If these warnings are meant to be there for future steps the user can resolve (might be a worthwhile follow-up walkthrough?), it would be good to mention that. As a user, I'm not sure I want to see warnings here that I don't know what to do with. It reduces confidence that this is a good course of action.

If these warnings are not meant to be here, we should possibly do something to resolve them in the imported openapi specfication.

The sequence of substeps (selecting Fruit Custom API connector and data mapper) does not represent what you have to follow in the UI. Which is confusing for a person who is new to the Fuse Online UI.

Error: Red Hat Fuse Online, Unable to provision. Please contact your Red Hat representative.

when clicking on Get Started at "Integrating message-oriented middleware with a RESTful API using AMQ Online"
Fuse Online is marked with ! on the right hand side.
Going to Service Catalog on the top link to Fuse Online works perfect.
environment is provisioned through RHPDS.

No need for this instruction, already clicked.

Originally posted by @briandooley in #92

On walkthrough "Managing and protecting APIs using API management" Task 3
Step 3.2 "Adding the Fuse Aggregation App Endpoint to Red Hat 3scale" the "3scale Private Base URL" placeholder is not being replace by the real URL.

See screenshot:

While working through the first walkthrough (FANTASTIC by the way - I love these), I noticed a minor inconsistency...

Each set of steps in 2.1, 2.2, and 2.3 starts with:

1. Log in to the Red Hat Fuse Online console.

And then goes on to do things in the Fuse Online console.

But 3.1 starts with

1. Select Integrations from the left hand menu.

Should we revise that to include a step for logging into the Red Hat Fuse Online console again for consistency?

When I run walkthroughs-2 for the first user, e.g evals01, everthing works perfect.
When I run it later for another user, e.g. evals02, I fail at step 1: 7. Authorize your Github Account
https://launcher-sso-launcher.apps.wien-e496.openshiftworkshop.com returns

We're sorry...
Federated identity returned by github is already linked to another user.

Problem is understandable, because I have only one place where I register the Github OAuth App...
see https://github.com/integr8ly/installation#add-the-generated-authorization-callback-url-to-github-oauth

How should this work with multiple users?
Do I miss something?