kyungjunleeme opened a new issue, #49171:
URL: https://github.com/apache/airflow/issues/49171

   ### Description
   
   ## [FEATURE] Proposal: Add Naver Cloud Airflow Provider
   
   Hi Airflow maintainers šŸ‘‹
   
   I'd like to propose adding an **Airflow provider for Naver Cloud Platform 
(NCP)**.  
   https://www.ncloud.com/
   While some of its services (like Object Storage) are compatible with AWS S3 
APIs and work with `S3Hook` by overriding the `endpoint_url`, many others are 
**Naver-specific** and not covered by existing AWS or GCP providers.
   
   ### šŸ” Why a separate provider is needed
   
   Naver Cloud offers various services unique to its ecosystem:
   
   - Sub Account (IAM alternative)
   - Cloud DB for MySQL, MSSQL, Redis
   - Ncloud Monitoring, Logging
   - Ncloud Function
   - Ncloud VPC & Firewall Management
   
   These services require Naver-specific APIs and authentication mechanisms 
(e.g., access key/secret with custom HMAC headers), which cannot be fully 
supported using existing AWS/GCP providers.
   
   ### āœ… What I plan to contribute
   
   - `NaverCloudHook` to handle API authentication and requests
   - One or more initial operators (e.g., for managing Cloud DB instances)
   - Documentation and examples
   
   Before starting, I’d like to hear:
   - Is the community open to adding a new provider for Naver Cloud?
   - Are there any special requirements or overlap considerations I should be 
aware of?
   
   Thanks in advance for your feedback!
   
   
   ### Use case/motivation
   
   _No response_
   
   ### Related issues
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [x] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to