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

Change precedence of droplet name config values #248

Conversation

davidmyersdev
Copy link

This PR actually requires that PR #247 gets merged in as well, but if it does, this PR will fix issue #234. It seems that config.vm.hostname overrides provider.name, and I don't believe this is the intended functionality. By allowing users to override config.vm.hostname with the optional provider.name to set the droplet name, we would be allowing the plugin to be more configurable by the user. There are instances where the config.vm.hostname and provider.name options could be different values, and this new order would allow each to still function properly.

@davidmyersdev
Copy link
Author

@seth-reeser this PR is obviously not useful since the dependent PR (#247) was closed. I also feel that giving the hostname precedence makes more sense now (since it can be defined within each config.vm.define statement independently). Thanks again!

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 this pull request may close these issues.

1 participant