-
Notifications
You must be signed in to change notification settings - Fork 10
[Pull Request] Merged Refactoring codes to Master #359
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
base: feature-refactoring
Are you sure you want to change the base?
[Pull Request] Merged Refactoring codes to Master #359
Conversation
Signed-off-by: ImMin5 <mino@megazone.com>
Modify analyze Daily date range 1 month -> 31days
Signed-off-by: ImMin5 <mino@megazone.com>
Modify budget and budget usages all apis
Signed-off-by: ImMin5 <mino@megazone.com>
Remove unused files
Signed-off-by: ImMin5 <mino@megazone.com>
Add convert model decorator at budget usage analyze api
Signed-off-by: ImMin5 <mino@megazone.com>
Signed-off-by: ImMin5 <mino@megazone.com>
Signed-off-by: ImMin5 <mino@megazone.com>
Add budget alert notification function
Signed-off-by: ImMin5 <mino@megazone.com>
Signed-off-by: ImMin5 <mino@megazone.com>
Signed-off-by: ImMin5 <mino@megazone.com>
Add logic for project based budget
Signed-off-by: ImMin5 <mino@megazone.com>
Signed-off-by: ImMin5 <mino@megazone.com>
Signed-off-by: ImMin5 <mino@megazone.com>
Signed-off-by: ImMin5 <mino@megazone.com>
# Conflicts: # src/spaceone/cost_analysis/interface/grpc/budget_usage.py # src/spaceone/cost_analysis/manager/budget_manager.py # src/spaceone/cost_analysis/manager/budget_usage_manager.py # src/spaceone/cost_analysis/manager/email_manager.py # src/spaceone/cost_analysis/manager/identity_manager.py # src/spaceone/cost_analysis/model/__init__.py # src/spaceone/cost_analysis/model/budget/request.py # src/spaceone/cost_analysis/model/budget/response.py # src/spaceone/cost_analysis/model/budget_usage/request.py # src/spaceone/cost_analysis/model/budget_usage/response.py # src/spaceone/cost_analysis/service/budget_service.py # src/spaceone/cost_analysis/service/budget_usage_service.py # src/spaceone/cost_analysis/service/cost_report_serivce.py # src/spaceone/cost_analysis/service/unified_cost_service.py
Signed-off-by: ImMin5 <mino@megazone.com>
Modify field name notifications -> notification
Signed-off-by: ImMin5 <mino@megazone.com>
…tification checks Signed-off-by: ImMin5 <mino@megazone.com>
Add error handling for unverified budget managers and update notification checks
…or budget usage notification logic Signed-off-by: ImMin5 <mino@megazone.com>
Signed-off-by: ImMin5 <mino@megazone.com>
Enhance budget management with optional workspace_id and refactor budget usage notification logic
Signed-off-by: seolmin <seolmin@megazone.com>
Signed-off-by: ImMin5 <mino@megazone.com>
Add budget state field and improve budget usage update logic
… state management Signed-off-by: ImMin5 <mino@megazone.com>
Implement budget state update job scheduling and enhance budget state management
Signed-off-by: ImMin5 <mino@megazone.com>
Add service_account_id field to budget usage model
… filter Signed-off-by: ImMin5 <mino@megazone.com>
Add service_account_id field to budget usage list request query filter
Migrate cost report services to UnifiedCost model
…ster Revert "Migrate cost report services to UnifiedCost model"
Signed-off-by: ImMin5 <mino@megazone.com>
…-pg-filter Add Unified cost analysis with domain_id filtering and project_group_id
Signed-off-by: ImMin5 <mino@megazone.com>
Add error handling for duplicated budget thresholds
Signed-off-by: ImMin5 <mino@megazone.com>
Update workspace_id field to be optional when get budget info
# Conflicts: # src/spaceone/cost_analysis/manager/budget_manager.py # src/spaceone/cost_analysis/manager/budget_usage_manager.py # src/spaceone/cost_analysis/service/budget_service.py
✅ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO. Contributors sign-off that they adhere to these requirements by adding a
Git even has a
|
✅ Why it is requiredThe Developer Certificate of Origin (DCO) is a lightweight way for contributors to certify that they wrote or otherwise have the right to submit the code they are contributing to the project. Here is the full text of the DCO. Contributors sign-off that they adhere to these requirements by adding a
Git even has a
|
Category
Description
[Pull Request] Merged Refactoring codes to Master