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

Deprecate Metal Facilities #312

Closed
displague opened this issue Apr 6, 2023 · 0 comments · Fixed by #314
Closed

Deprecate Metal Facilities #312

displague opened this issue Apr 6, 2023 · 0 comments · Fixed by #314

Comments

@displague
Copy link
Member

displague commented Apr 6, 2023

Equinix Metal has announced the deprecation of facilities as a provisioning parameter:

This deprecation allows some users to continue to use the feature until a later date.

Users of facilities should become aware of facility deprecation in a number of ways:

  • Equinix Metal's use of Deprecation and Sunset headers should be surfaced through Terraform output or logs
  • fields should be marked as deprecation
  • docs should mark the field as deprecated (we don't get this for free through doc generation Generate docs with go generator #201
  • examples should be updated to not promote the use of facilities
  • the Facility -> Metro guide will need to be revised

Affected Resources

List generated with git grep "\`facil.*\`\ -" in the docs/ directory. Potentially other resources will need to be revised along with examples and guides.

  • data-sources/equinix_metal_connection.md:* facility - Slug of a facility to which the connection belongs.
  • data-sources/equinix_metal_device.md:* facility - The facility where the device is deployed.
  • data-sources/equinix_metal_hardware_reservation.md:* facility - Plan type for the reservation.
  • data-sources/equinix_metal_ip_block_ranges.md:* facility - (Optional) Facility code filtering the IP blocks. Global IPv4 blocks will be listed
  • data-sources/equinix_metal_precreated_ip_block.md:* facility - (Optional) Facility of the searched block. (for non-global blocks).
  • data-sources/equinix_metal_spot_market_price.md:* facility - (Optional) Name of the facility.
  • data-sources/equinix_metal_spot_market_request.md:* facilities - Facility IDs where devices should be created.
  • data-sources/equinix_metal_vlan.md:* facility - (Optional) Facility where the VLAN is deployed.
  • resources/equinix_metal_connection.md:* facility - (Optional) Facility where the connection will be created.
  • resources/equinix_metal_device.md:* facilities - (Optional) List of facility codes with deployment preferences. Equinix Metal API will go
  • resources/equinix_metal_reserved_ip_block.md:* facility - (Optional) Facility where to allocate the public IP address block, makes sense only
  • resources/equinix_metal_spot_market_request.md:* facilities - (Optional) Facility IDs where devices should be created.
  • resources/equinix_metal_vlan.md:* facility - (Required) Facility where to create the VLAN.

See Also

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant