Support for Metros
Closed this issue · 2 comments
This issue is a planning/placeholder for incoming work related to backend work in progress:
As information becomes available this description will be updated and comments will be added to support the implementation changes.
Depends on equinixmetal-archive/packngo#238
We wil need a new datasource:
- datasource
metal_metro#58
We will also need new metro properties. Generally, these will be optional and adjacent to facility. Facility will become optional, when metro is specified. The metro property will be a slug. Users can fetch additional metro details through a lookup on the metal_metro datasource.
The following need a read-only metro property:
- datasource metal_spot_market_request (Update: request_id is the only parameter, and device_ids the only attribute)
- datasource metal_spot_market_price metro parameter (make facility optional) #64
- datasource metal_ip_block_ranges metro filter #58
- datasource metal_precreated_ip_block metro property #58
- datasource metal_volume metro property (Update: volumes can not be metro scoped)
- datasource metal_facility metro property #31 #58
The following need an optional metro property as an alternative to the facility. One is required, the values should not conflict, but if they do the API response will handle that - we will not try to prevalidate.
- resource metal_device metro property #46
- resource metal_spot_market_request #63
- resource
metal_vlan#53 - resource
reserved_ip_block#56
Examples should be broadly be updated to demonstrate metros. A few smaller examples can demonstrate Facilities.
Looking for this to be implemented and merged by April 2.