Feature Requests

Anonymous

Feature Requests for Harness. Select 'Category' based on the module you are requesting the feature for.
Enhancement: Restrict Start/Stop Actions for CCM Viewer Role in Autostopping
Customer has reported that users assigned the ccm-viewer role can still perform Start and Stop actions on servers from the CCM Autostopping Rules UI. Since the ccm-viewer role is intended for view-only access, the customer expects users with this role to be restricted from performing operational actions that modify server states. The customer was previously informed that this behavior is by design. However, they would like to revisit this functionality and have Start/Stop actions restricted for users with view-only access. Current Behavior Users assigned the ccm-viewer role can access the Autostopping Rules UI. These users can perform Start and Stop actions on servers. There is currently no effective restriction preventing view-only users from triggering these operations. Expected Behavior Users assigned the ccm-viewer role should have read-only access to CCM Autostopping. Start and Stop actions should be hidden or disabled for users with view-only permissions. Only users with the appropriate permissions should be allowed to perform Start/Stop operations. Backend authorization should also enforce these restrictions to prevent unauthorized actions through API requests. Enhancement Request Introduce granular RBAC control for Start and Stop operations in CCM Autostopping. The enhancement should: Separate operational permissions (Start/Stop) from view-only permissions. Restrict Start/Stop actions for users assigned the ccm-viewer role. Ensure the UI and backend APIs consistently enforce the assigned permissions. Allow administrators to grant operational permissions independently of read-only access. Business Impact This limitation prevents customers from enforcing a strict separation between users who can monitor Autostopping configurations and users who are authorized to perform operational actions. For NYLI, this is an important access-control requirement to ensure that users with view-only access cannot inadvertently start or stop infrastructure resources.
1
·
Cloud Cost Management
·
under review
Time-aware (dynamic) budget alerts for CCM Perspectives
Make budget alert notifications context-aware by evaluating spend against the position within the budget period, so users are only alerted when the spending pace represents a real risk of overrun. Problem CCM Perspectives budgets currently support six threshold alerts (Actual 50/80/100% and Forecast 50/80/100%). Alerts fire purely on the percentage threshold, with no awareness of where we are in the budget period. Example: a "Forecast 50%" alert triggers the same way on day 5 of the month as on day 25 — even though these have very different financial meanings. This produces noise on normal spend patterns and dilutes the signal when a real risk exists. Requested behavior Introduce dynamic, time-aware budget notifications that evaluate both: Budget consumption percentage Progress through the budget period The platform should decide whether the current spending velocity indicates an elevated probability of exceeding the budget, and alert accordingly. Example (monthly budget, Forecast 50%) Day 8 → Notify. Velocity suggests likely overrun before month-end. Day 15 → Optional notification, depending on configurable tolerance. Day 25 → Do not notify. Normal spending behavior; no user attention needed. Suggested configurability Toggle between "Static thresholds" (today's behavior) and "Dynamic / time-aware" mode per budget. Configurable tolerance band for the "warning" zone. Applies to both Actual and Forecast alerts, across monthly / quarterly / yearly budget periods. Benefit Reduces alert fatigue, surfaces only financially meaningful risks, and improves budget governance across Perspectives.
2
·
Cloud Cost Management
·
pending feedback
Load More
→