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

provider/openstack: Add 'value_specs' option to 'openstack_fw_policy_v1' resource #9835

Merged

Conversation

fatmcgav
Copy link
Contributor

@fatmcgav fatmcgav commented Nov 3, 2016

Refactor to use common 'types.go' and 'MapValueSpecs' function.
Website docs updated to reflect additions

WIll require re-base after #9830 and #9834 are merged

@fatmcgav
Copy link
Contributor Author

fatmcgav commented Nov 3, 2016

@jtopjian 2nd of 3 resources :)

…v1' resource

Refactor to use common 'types.go' and 'MapValueSpecs' function.
Website docs updated to reflect additions
@fatmcgav fatmcgav force-pushed the openstack_fw_policy_v1_add_value_specs branch from bbe4dc7 to d3b2c15 Compare November 4, 2016 19:06
@fatmcgav
Copy link
Contributor Author

fatmcgav commented Nov 4, 2016

@jtopjian Rebased after merge of #9830 and #9834

@jtopjian jtopjian merged commit 5efe1a7 into hashicorp:master Nov 5, 2016
@fatmcgav fatmcgav deleted the openstack_fw_policy_v1_add_value_specs branch November 5, 2016 16:23
@ghost
Copy link

ghost commented Apr 20, 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 20, 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