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

Latest updates #59

Merged
merged 17 commits into from
Apr 13, 2017
Merged

Latest updates #59

merged 17 commits into from
Apr 13, 2017

Conversation

mikejihbe
Copy link
Contributor

Closes #50, Closes #44, Closes #49.

It also makes route table attributes optional, which I believe will resolve #34.

It also adds documentation for iscsi attributes, Closes #12.

mikejihbe and others added 17 commits April 3, 2017 21:14
`baremetal_core_subnet.security_list_ids` with multiple items causes
destroy/add on every `terraform apply`, even with no changes. API state
does not respect item ordering, so config and API state do not match
(except when items happen to have exactly the same sorting as used by
API state). Because local and remote state do not match, terraform will
attempt to change remote state to match on every `apply`.

Change `security_list_ids` from `TypeList` to `TypeSet`, so terraform
only considers membership, not ordering.

Fixes oracle#44
subnet: fix security_list_ids ordering
@craigcarl-oracle craigcarl-oracle merged commit d5ed903 into oracle:master Apr 13, 2017
@kilokahn kilokahn added the listVsSet Customer issues arising from diffs due to ambiguity between list and set usage label Jul 24, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
listVsSet Customer issues arising from diffs due to ambiguity between list and set usage
Projects
None yet
4 participants