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

require credentials when creating a provider #16

Merged
merged 1 commit into from
Aug 11, 2017
Merged

require credentials when creating a provider #16

merged 1 commit into from
Aug 11, 2017

Conversation

jntullo
Copy link

@jntullo jntullo commented Aug 10, 2017

manageiq-api version of ManageIQ/manageiq#15528

Currently, credentials are not required when creating a new provider via the api, which differs from the Classic UI which requires that credentials be added. This PR makes credentials required if there are no connection attributes specified (container providers only supply connection attributes)

BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1467692

@miq-bot assign @abellotti

@miq-bot
Copy link
Member

miq-bot commented Aug 10, 2017

@jntullo Cannot apply the following label because they are not recognized: bz

@miq-bot
Copy link
Member

miq-bot commented Aug 10, 2017

Checked commit jntullo@a6ce25d with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0
2 files checked, 0 offenses detected
Everything looks fine. 👍

@abellotti abellotti added this to the Sprint 67 Ending Aug 21, 2017 milestone Aug 11, 2017
@abellotti abellotti added the bug label Aug 11, 2017
@abellotti
Copy link
Member

LGTM!!! Thanks @jntullo 👍

@abellotti abellotti merged commit 441738c into ManageIQ:master Aug 11, 2017
@simaishi
Copy link
Contributor

@jntullo @abellotti Can/should this be backported to Fine branch? The associated BZ has the backport flag set.

@simaishi
Copy link
Contributor

simaishi commented Oct 4, 2017

@jntullo @abellotti ^ ping

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

Successfully merging this pull request may close these issues.

4 participants