DigitalOcean will change their floating IP API on the 26th of april

未关闭
#1,574 1 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
2/5
预计耗时
1-3 小时
新手友好度
50/100
Issue 类型
缺陷
描述清晰度
描述清楚
活跃度
停滞
技术栈
python
领域
cloud

调研方向

首先查看 libcloud/test/compute/fixtures/digitalocean_v2/list_floating_ips.json 和 create_floating_ip.json,以及使用它们的 DigitalOcean compute 测试。将这些 fixture 与已公布的 Floating IP API 响应变更进行比较,然后运行相关测试,并确认这些 fixture 表示了更新后的响应字段。

由索引模型根据 Issue 内容生成。

描述

api: compute drivers: digitalocean stale

We just got an email from DigitalOcean stating that they will change their Floating IP API endpoint starting the 26th. Functionally this shouldn't break in libcloud but the fixtures for the tests that are used will be a bit outdated (https://github.com/apache/libcloud/blob/trunk/libcloud/test/compute/fixtures/digitalocean_v2/list_floating_ips.json)

Changes announced by DigitalOcean:

The `private_networking` feature will now be listed under droplet.features instead of region.features
vpc_uuid was not being populated and will have the correct values now
The droplet.type will be "base" when the droplet is a base image (i.e. Ubuntu, CentOS).
The current value is "snapshot"
The Droplet's networking field will include any private IPs and any floating IPs which are missing from the response today

Test fixtures that would become 'inaccurate':
https://github.com/apache/libcloud/blob/trunk/libcloud/test/compute/fixtures/digitalocean_v2/list_floating_ips.json
https://github.com/apache/libcloud/blob/trunk/libcloud/test/compute/fixtures/digitalocean_v2/create_floating_ip.json

主要语言
Python
星标
2.1k
派生
935
平均合并
5 天 3 小时
30 天内合并 PR
15

环境准备

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

apache/libcloud 的其他 Issue

查看 apache/libcloud 的全部 Issue

相似的 Issue

更多 Python Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。