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

Endpoint for provider regions. #580

Closed
Hyperkid123 opened this issue Apr 30, 2019 · 3 comments · Fixed by #581
Closed

Endpoint for provider regions. #580

Hyperkid123 opened this issue Apr 30, 2019 · 3 comments · Fixed by #581
Assignees

Comments

@Hyperkid123
Copy link
Contributor

Hyperkid123 commented Apr 30, 2019

Is it possible to create endpoint to list provider regions?

expected output is this:

{
"ManageIQ::Providers::Amazon::CloudManager": [
  {
    "name": "Asia Pacific (Mumbai)",
    "id": "ap-south-1"
  }, {
    "name": "Asia Pacific (Seoul)",
    "id": "ap-northeast-2"
  }],
"ManageIQ::Providers::Azure::CloudManager": [
  {
    "name": "Australia Central",
    "id": "australiacentral"
  }]
}

Currently is done by this method in ui-classic: https://github.com/ManageIQ/manageiq-ui-classic/blob/d8898f12e852b23bb0fceaefb9614a956a828a9c/app/controllers/mixins/ems_common.rb#L562

I want to be able to get provider regions for specific provider type (currently just Cloud providers). It does not have to be in that exact format, it can be just one collection with some provider type attribute or something like that.

cc @skateman

@Hyperkid123
Copy link
Contributor Author

@miq-bot assing @skateman

@miq-bot
Copy link
Member

miq-bot commented Apr 30, 2019

@Hyperkid123 unrecognized command 'assing', ignoring...

Accepted commands are: add_label, add_reviewer, assign, close_issue, move_issue, remove_label, rm_label, remove_reviewer, set_milestone

@Hyperkid123
Copy link
Contributor Author

@miq-bot assign @skateman

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

Successfully merging a pull request may close this issue.

3 participants