Skip to content
This repository has been archived by the owner on Aug 28, 2023. It is now read-only.

Include to Red Hat Cloud services into shortcuts #30

Open
PanSpagetka opened this issue Jul 29, 2019 · 7 comments
Open

Include to Red Hat Cloud services into shortcuts #30

PanSpagetka opened this issue Jul 29, 2019 · 7 comments
Labels

Comments

@PanSpagetka
Copy link
Contributor

In My Settings -> Visual (at the bottom of the screen) user can customize what page will show after login. Should we also include Red Hat Cloud Services? It would probably meant make miq_shortcuts.yml also plugable.

@h-kataria @Fryguy @martinpovolny What do you think?

@h-kataria
Copy link
Contributor

@PanSpagetka yes, i think we should look into making miq_shortcuts.yml plugable, that will help with moving v2v shortcuts out of the yaml as well and any such future shortcuts. @GregP has been looking into a BZ to add missing shortcuts, should he wait and not add Red Hat Cloud Services shortcuts into the yaml?
@Fryguy @martinpovolny what are your thoughts, i am not sure how much amount of work that is.

@GregP
Copy link

GregP commented Jul 29, 2019 via email

@agrare
Copy link
Member

agrare commented Jul 29, 2019

@GregP @h-kataria we can't have any reference to RedHatCloudServices in upstream manageiq as it is a downstream only gem

@GregP
Copy link

GregP commented Jul 29, 2019 via email

@martinpovolny
Copy link
Contributor

@GregP @h-kataria we can't have any reference to RedHatCloudServices in upstream manageiq as it is a downstream only gem

Then we need the miq_shortcuts.yml pluggable as @h-kataria wrote or get rid of the whole MiqShortcut idea.

Or... ... at least for now do not add Cloud Services there and simply do not allow it to be the starting page (which probably does not make much sense anyway).

@agrare
Copy link
Member

agrare commented Jul 30, 2019

Yeah until we have pluggable miq_shortcuts lets just not have cloud services as an option

@miq-bot miq-bot added the stale label Feb 3, 2020
@miq-bot
Copy link

miq-bot commented Feb 3, 2020

This issue has been automatically marked as stale because it has not been updated for at least 6 months.

If you can still reproduce this issue on the current release or on master, please reply with all of the information you have about it in order to keep the issue open.

Thank you for all your contributions!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Projects
None yet
Development

No branches or pull requests

6 participants