You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/config.md
+9-9Lines changed: 9 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -90,7 +90,7 @@ securityGroups:
90
90
- uuid: < your security group ID >
91
91
- name: < your security group Name >
92
92
- filter:
93
-
project_id: < you project ID >
93
+
projectId: < you project ID >
94
94
tags: < a tag >
95
95
- name: < your security group Name >
96
96
filter:
@@ -124,19 +124,19 @@ Rather than just using a network, you have the option of specifying a specific s
124
124
If you have a complex query that you want to use to lookup a network, then you can do this by using a network filter. The filter will allow you to look up a network by the following network features:
125
125
- status
126
126
- name
127
-
- admin_state_up
128
-
- tenant_id
129
-
- project_id
127
+
- adminStateUp
128
+
- tenantId
129
+
- projectId
130
130
- shared
131
131
- id
132
132
- marker
133
133
- limit
134
-
- sort_key
135
-
- sort_dir
134
+
- sortKey
135
+
- sortDir
136
136
- tags
137
-
- tags-any
138
-
- not-tags
139
-
- not-tags-any
137
+
- tagsAny
138
+
- notTags
139
+
- notTagsAny
140
140
141
141
By using filters to look up a network, please note that it is possible to get multiple networks as a result. This should not be a problem, however please test your filters with `openstack network list` to be certian that it returns the networks you want. Please refer to the following usage example:
0 commit comments