Cloud-init patch is removing support for some cloud providers
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 3.2k
- Forks
- 692
- PR merge metrics
- No merged PRs in 30d
Description
The cloud-init config looks to be explicitly disabling support for several cloud provider datasources.
I only noticed this while looking for something else, so I haven't reproduced the issue, but fairly certain https://vmware.github.io/photon/assets/files/html/3.0/photon_installation/set-up-PhotonOS-on-ec2.html cloud-init steps will work.
This may have been unintentionally introduced as part of 1104cc7f83cd5bbaaa50027b29114ca70d53b159 cc @sshedi
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with SPECS/cloud-init/cloud-cfg.patch at lines 54-61 and compare the referenced commit to determine which datasource support is disabled. Review the PhotonOS EC2 cloud-init setup guide and check the affected provider configurations. Done means confirming the regression and restoring support without breaking the intended patch behavior.
Written by the indexing model from the issue text.
Assessment
- Domain
- cloud, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100