oracle / oracle/oci-python-sdk
Removal of IMDS v1 Fallback from oci-python-sdk
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 474
- Forks
- 321
- Avg merge
- 23m
- Merged PRs (30d)
- 4
Description
This issue tracks the removal of fallback to IMDS v1 endpoints and the introduction of retry logic for IMDS v2 in oci-python-sdk
IMDS (Instance Metadata Service) endpoints provide region information and metadata for Instance Principal, Resource Principal, and etc. To ensure the security and functionality of this feature, IMDS v1 fallback will be removed from all SDKs. After this change, if the IMDS v2 endpoint is unavailable, there will be no fallback to IMDS v1. Applications relying on v1 fallback must update accordingly to avoid service disruptions.
Changes Implemented
Remove Fallback to IMDS v1:
The SDK will no longer attempt to access IMDS v1 if IMDS v2 requests fail.
Retry Mechanism for IMDS v2 in Auth:
A retry strategy has been introduced with 8 retry attempts and exponential backoff with Jitter between attempts
This change will take effect starting from the version 2.141.0
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
The issue names no files, tests, or entry points. Start by locating IMDS handling in the SDK's authentication code, then inspect how failed IMDS v2 requests are handled. Done means IMDS v1 fallback is absent and IMDS v2 retries use eight attempts with exponential backoff and jitter.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authentication, cloud, security
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100