You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 23, 2020. It is now read-only.
In many cases, when a user logs into OSIO, they might already have some project / namespace or app deployed in their OSO space. Since we need to config this namespace as the users dev environment, we should handle the condition gracefully, doing either one of the following options:
When the user logs into OSIO, they are asked to link their OSO account - at this point, we should sanity check their OSO account to ensure its in a good state, if not, offer the user a choice to clean it up for them
Alternatively, we just use whatever project the tenant already has setup, as their dev environ and just modify that space with whatever acl's and privileges we need.
The first choice sounds like a smaller task - build a tool to examine a user's environment, and if the state does not match our predefined concept of a "good" state, clean it up.
The second choice sounds more involved as we would be performing discrete modifications to a user's environment.
The challenge is that this project/dev environment needs to live in a space somewhere. I think the ideal situation here long term is that we would have a unique UI flow to handle this situation, as it may be a likely situation for many people on-boarding into OSIO. I can add this to the UX Backlog. If we want to do a fix until then, I agree that asking the users to clean if we see this is a fine hold-over until we can implement the proper pathway.
In many cases, when a user logs into OSIO, they might already have some project / namespace or app deployed in their OSO space. Since we need to config this namespace as the users dev environment, we should handle the condition gracefully, doing either one of the following options:
Sub-task(s):
The text was updated successfully, but these errors were encountered: