"Reset Environment" should cleanup custom tenant config

[ibuziuk]

fabric8 PR verification is a super cool feature and everyone can test new version of tenant by navigating to URL e.g. [1] and pushing "Save and Update Tenant" button. However, resetting this configuration is not very straight forward - one should navigate to the profile tenant page [2] and push "Clear Values" button.
At very least "Reset Environment" from profile page should also do custom tenant config cleanup.

[1] https://openshift.io/_profile/_tenant?cheVersion=PR-v8fa786e-12&mavenRepo=https://nexus.cd.test.fabric8.io/content/repositories/staging
[2] https://openshift.io/_profile/_tenant

Parent Experience

#2156 Tenant Override Screen placeholder

[benoitf]

I faced the same issue, I was expecting that reset env button was also clearing up all tenant config but it was not the case.

[joshuawilson]

@ibuziuk what are you asking for? Are you asking for some UX on this back door?

[ibuziuk]

@joshuawilson it is a back door currently and some trivial back-end validation of maven repo / checksum for sure must be in place

[joshuawilson]

I think I misunderstood the first time. @ibuziuk we should talk to @catrobson about designing a better user flow for this page.

[qodfathr]

Is this still an issue? Our goal is to remove the need for the "Reset Environment" button. Is this mainly serving an internal need?

[joshuawilson]

I think we should consider keeping this. On the free tier the user may want to play around and then reset. I reset just to clean up so I don't have to do it manually.

[ldimaggi]

+1 to keeping it. Thx!

…

On Mon, Jan 22, 2018 at 1:51 PM, Joshua Wilson ***@***.***> wrote: I think we should consider keeping this. On the free tier the user may want to play around and then reset. I reset just to clean up so I don't have to do it manually. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#1049 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAnOPaJ6lFYEG_6TdNsBTm7d7bQPrgK0ks5tNNizgaJpZM4PsM0j> .

-- Len DiMaggio (ldimaggi@redhat.com) JBoss by Red Hat 314 Littleton Road Westford, MA 01886 USA tel: 978.392.3179 cell: 781.472.9912 http://www.redhat.com http://community.jboss.org/people/ldimaggio

[qodfathr]

Okay, now I'm even more confused. :)

Are we saying that this issue needs to be addressed directly?
Are we saying that the Reset Env button should not go away?
Are we saying this is all moot because the Reset Env button is going to go away?

Personally, I really want to see the Reset Env button go away. IMHO, it's existence is being used crutch to avoid fixing bugs. I never enjoy having to push that button, especially now that I have dozens of Spaces.

If the original request of this Issue is serving an internal-need only, then I'd prefer to see us adopt an internal only solution (e.g. perhaps the Reset Env button is Feature Flagged to be Internal or we have and additional internal-only button which can address this particular issue.)

[aslakknutsen]

@qodfathr Agree that this feature should be hidden from normal usage. It's to destructive during normal usage of the system, and really only valuable for test envs or test users. The users need for this will go away when Space:Delete takes OSO space related resources into account on Delete: #1746

But, to @ibuziuk's point; 'Should it also remove tenant overrides set on the account?", I think if we move "Reset Env" to the "Tenant override page" and away from the "User Profile Edit", then it would become clearer what you are Resetting the env to as you can see the Override set on the same screen.

[qodfathr]

@aslakknutsen are you suggesting a new Tenant Override page? Or is that some hidden thing that already exists? Regardless, I agree with the value for the scenarios you described.

[ldimaggi]

I'm fine with the feature being hidden - but it should not be removed. Users, especially new users, and users experimenting with OSIO will require access to a cleaned environment.

[aslakknutsen]

@qodfathr It's a thing that exists, but usage is restricted to 'Internal'.

[sthaha]

Removing team/build-cd since it doesn't seem like an issue related to build. Additionally this feature request must be tracked in Planner