-
Notifications
You must be signed in to change notification settings - Fork 4
Validation for Environment #20
Comments
In the first version we will probably auto-generate namespaces. It will simplify managing namespaces in tenant service. Not sure when we would want to generate them. We could do it during env creation if lazy provisioning is tricky. |
@alexeykazakov For namespaceName, so it seems that we want to postpone this for now. |
@alexeykazakov @dipak-pawar For clusterApiURL, when we creating new_env we also get clusterURL in create_payload. We should check that the clusterURL in create_payload is valid cluster_url and the user who is creating new_env has access (or linked) the given cluster_url. Do we have have any API in cluster_service to check the same ?? |
@nurali-techie, We have |
That should be easy to do by asking tenant service - there is already such an endpoint: http://swagger.goa.design/?url=github.com%2Ffabric8-services%2Ffabric8-tenant%2Fdesign#!/tenants/tenants_search
This has to be done in tenant service - to avoid conflicts. There is already a logic that generates the names - it uses information from tenant DB. The tricky thing is that newly the namespaceName can change, for more information see this issue and PR |
For namespaceName,
For clusterApiURL,
The text was updated successfully, but these errors were encountered: