1
0
mirror of https://github.com/peeringdb/peeringdb.git synced 2024-05-11 05:55:09 +00:00

api_specs 'irr_as_set' fix, deploy.md update (#854)

* api_specs: 'irr_as_set' is actually a string, not a set.

* Update deploy.md: ^python2.7^python3.7
This commit is contained in:
Chris Caputo
2020-11-03 16:27:53 -08:00
committed by GitHub
parent a6d824da58
commit 2ca4eb96de
3 changed files with 4 additions and 4 deletions

View File

@@ -47,7 +47,7 @@ deleted in that timeframe as well - you can spot them by checking for status "de
### Nested data
Any field ending in the suffix **_set** is a list of objects in a relationship with the parent
Any field ending in the suffix **_set** (with the exception of 'irr_as_set') is a list of objects in a relationship with the parent
object, you can expand those lists with the 'depth' parameter as explained below.
The naming schema of the field will always tell you which type of object the set is holding
@@ -59,7 +59,7 @@ So a set called 'net_set' will hold Network objects (api endpoint /net)
### Depth
Nested sets will not be loaded (any field ending with the _set suffix) unless the 'depth'
Nested sets will not be loaded (any field ending with the _set suffix, with the exception of 'irr_as_set') unless the 'depth'
parameter is passed in the request URL.
Depth can be one of three values:

View File

@@ -2,7 +2,7 @@
### Depth
Nested sets will not be expanded (any field ending with the _set suffix) unless the 'depth'
Nested sets will not be expanded (any field ending with the _set suffix, with the exception of 'irr_as_set') unless the 'depth'
parameter is passed in the request URL.
Depth can be one of three values:

View File

@@ -1,7 +1,7 @@
# PeeringDB Deploy
PeeringDB currently only runs on python2.7 - all instructions below are to be taken with that in mind.
PeeringDB currently only runs on python3.7 - all instructions below are to be taken with that in mind.
## Updates and formatting