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

fixes #19616 - use fog-digitalocean gem #17

Merged
merged 1 commit into from
May 28, 2017

Conversation

domcleal
Copy link
Contributor

@domcleal domcleal commented May 22, 2017

For compatibility with Foreman 1.16.0+. The plugin's major version number should probably be incremented on release.

@theforeman-bot
Copy link
Member

There were the following issues with the commit message:

  • 1fc9f7f must be in the format fixes #redmine_number - brief description

If you don't have a ticket number, please create an issue in Redmine.

More guidelines are available in Coding Standards or on the Foreman wiki.


This message was auto-generated by Foreman's prprocessor

Fog 1.40.0 (as used in Foreman 1.16+) has extracted the DO provider into
the fog-digitalocean gem, renaming the classes to remove the version
number. This is incompatible with older Fog and Foreman releases.

Also renames the Fog extensions to match Rails autoloader standards.
@timogoebel timogoebel merged commit 9eed06d into theforeman:master May 28, 2017
@timogoebel
Copy link
Member

Merged, thanks @domcleal.

@dLobatog
Copy link
Member

Nice, I was planning on merging this as soon as I had a minute but you beat me to it 😄 I'll try to do the 2.0 release today.

@timogoebel
Copy link
Member

I'll try to do the 2.0 release today.

As discussed on irc, let's wait for core 1.16 release before doing that.

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

Successfully merging this pull request may close these issues.

4 participants