Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Better naming for keys #10178

Closed
bdunne opened this issue Aug 1, 2016 · 6 comments
Closed

Better naming for keys #10178

bdunne opened this issue Aug 1, 2016 · 6 comments

Comments

@bdunne
Copy link
Member

bdunne commented Aug 1, 2016

The current keys used to find the correct provision type are not specific enough. Once Vmware Cloud provisioning is added, Vmware Infra provisioning will break due to the naming and constant lookup ordering.
#10102 was a temporary workaround because changing the keys is a much larger project.

@bdunne
Copy link
Member Author

bdunne commented Aug 1, 2016

cc @gmcculloug

@gmcculloug
Copy link
Member

@miq-bot
Copy link
Member

miq-bot commented Aug 26, 2017

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!

@miq-bot miq-bot added the stale label Aug 26, 2017
@gmcculloug gmcculloug added pinned and removed stale labels Aug 31, 2017
@chessbyte
Copy link
Member

@bdunne still an issue?

@bdunne
Copy link
Member Author

bdunne commented Oct 17, 2019

It hasn't been fixed yet.

@gmcculloug gmcculloug removed their assignment Apr 7, 2020
@gtanzillo
Copy link
Member

Closing as this will be handled with the pluggability work in issue #19440

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

No branches or pull requests

5 participants