Pull the projects list from OC

[sino92]

Is your feature request related to a problem? Please describe. After hitting modify an existing project and go through the list, we see projects that are already removed from OCP.

Describe the solution you'd like Get the list of projects using an oc command

Describe alternatives you've considered none

Additional context none

[sino92]

@michaelsauter @clemensutschig @stitakis @oalyman Thoughts?

[stitakis]

I think it makes a lot of sense to use openshift as the source for the project list.

[michaelsauter]

Another issue with the current approach is that you do NOT see projects that were migrated to a cluster. Since the provisioning app did not create the project, it does not know about it, so you cannot modify it :(

I am a bit unsure about the overall fit of this though. If the prov-app has direct access to OCP projects now, then this could raise the question if it shouldn't do the provisioning itself too, instead of going via Jenkins. However, I'm just raising this point so that we are aware of it - I'm still in favour of the proposed change.

[oalyman]

• currently, you can provision a project and tick off to create open shift resources. So we need to change that if we want to use OS as source of truth.
• what about the additional metadata that is currently stored in the local storage?
• what namespaces should be visible to the provisioning app? In some environments you might not want to have all namespaces to be exposed to be modified

[stitakis]

Please see my comment to the 3 points mentioned by @oalyman

1. currently, you can provision a project and tick off to create open shift resources. So we need to change that if we want to use OS as source of truth.

Do we want to be able to provision components to bitbucket with prov-app if the corresponding openshift project does not exists? If is not the case, then nothing to do here. If yes, then we need to think about a solution.

2. what about the additional metadata that is currently stored in the local storage?

Is any metadata needed to fill the drop-down list? @sino92: can you please verify?

3. what namespaces should be visible to the provisioning app? In some environments you might not want to have all namespaces to be exposed to be modified

Ideally I would display the list of projects that my user is permitted to provision to. Make sense?

[sino92]

As the metadata, we'd need the component information of an existing OC project. We can use the project name to retrieve that information from OpenProjectData. The new class to pull existing OC projects won't replace LocalStorage.