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

Rename graphNodeMissingProvider to graphNodeProvider #4999

Merged
merged 1 commit into from
Feb 8, 2016
Merged

Rename graphNodeMissingProvider to graphNodeProvider #4999

merged 1 commit into from
Feb 8, 2016

Conversation

svanharmelen
Copy link
Contributor

It seems graphNodeProvider is a more descriptive name for this node…

It seems `graphNodeProvider` is a more descriptive name for this node…
@svanharmelen
Copy link
Contributor Author

@phinze as discussed I moved the renaming of graphNodeMissingProvider into it's own PR. PR #4877 now only contains changes to the provisioner related code.

@svanharmelen
Copy link
Contributor Author

@phinze if you can spare 30 seconds to double check this one, we can sync the provider naming with the provisioner naming again. Thx!

@phinze
Copy link
Contributor

phinze commented Feb 8, 2016

LGTM!

@svanharmelen
Copy link
Contributor Author

Thx!

svanharmelen pushed a commit that referenced this pull request Feb 8, 2016
…node

Rename `graphNodeMissingProvider` to `graphNodeProvider`
@svanharmelen svanharmelen merged commit f6822dc into hashicorp:master Feb 8, 2016
@svanharmelen svanharmelen deleted the f-rename-missing-provider-node branch February 9, 2016 09:42
@ghost
Copy link

ghost commented Apr 28, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Apr 28, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants