Deze pagina is nog niet beschikbaar in uw eigen taal. We werken er hard aan om meer taalversies toe te voegen. Bedankt voor uw steun.
Cloud Operations Center
Cloud Operations Center
- Service Overview
- Getting Started
-
User Guide
- COC Enablement and Permissions Granting
- Overview
-
Resources
- Resource Management
-
Application Management
- Overview
- Creating an Application
- Modifying an Application
- Deleting an Application
- Application Topology
- Creating a Component
- Modifying a Component
- Deleted a Component
- Creating a Group
- Modifying a Group
- Deleting a Group
- Manually Associating with Resources
- Automatically Associating with Resources
- Transferring Resources
- Disassociating Resources from an Application Group
- Viewing Resource Details
- Viewing Capacity Details
- Resource O&M
- Automated O&M
-
Faults
- Diagnosis Tools
- Alarms
-
Incident Management
- Incidents
- Creating an Incident
- Rejecting an Incident
- Resubmitting an Incident After Rejection
- Forwarding Incidents
- Handling Incidents
- Upgrading/Downgrading an Incident
- Adding Remarks
- Starting a War Room
- Handling an Incident
- Verifying Incident
- Creating an Improvement Ticket For An Incident
- Incident History
- WarRoom
- Improvement Management
- Issue Management
- Forwarding Rules
- Data Source Integration Management
- Change Management
- Resilience Center
- Task Management
- Basic Configurations
- Viewing Logs
- Best Practices
- API Reference
-
FAQs
- Product Consulting
- Resource Management FAQs
-
FAQs About Resource O&M
-
Patch Management FAQs
- What Can I Do If the Patch Baselines Do Not Take Effect?
- What Are the Differences Between the Installation Rule Baselines And User-defined Baselines?
- What Can I Do If Exception all mirrors were tried Is Recorded in the Patch Service Ticket Log?
- Why Can't I Select a Node?
- What Can I Do If the Compliance Report Still Reports Non-compliance for a Patch After the Patch Has Been Repaired?
- What Can I Do If the lsb_release not found Error Occurs During Patch Operations?
- Automation FAQs
- Batch Operation FAQs
- FAQs About Parameter Management
- Resource O&M Permissions and Supported Actions
-
Patch Management FAQs
- FAQs About Fault Management
- FAQs About Change Ticket Management
- Resilience Center FAQs
- Change History
On this page
Show all
Help Center/
Cloud Operations Center/
FAQs/
FAQs About Resource O&M/
FAQs About Parameter Management/
What Are the Permissions Required for Managing Parameters?
What Are the Permissions Required for Managing Parameters?
Updated on 2025-01-14 GMT+08:00
Permission design
- To access the parameter list page, the coc:parameter:list permission is required.
- To obtain parameter details, the coc:parameter:get permission is required.
- To delete a parameter, the operation permission coc:parameter:delete is required.
- To create a parameter, the operation permission coc:parameter:create is required.
- To update a parameter, the operation permission coc:parameter:update is required.
- Resource permissions: coc:*:*:parameter:name (The first asterisk (*) indicates all region IDs, the second asterisk (*) indicates all tenants, and name indicates the parameter name. This permission means that you can access a parameter of the specified tenant in a certain region.)
Resource permissions determine the data that you can access. Operation permissions are used to perform operations on your resource permissions. Common problems are as follows:
- If you can access a parameter but cannot access the parameter list page, you do not have the coc:parameter:list permission.
- If you cannot find a specified parameter, check whether you have the permission on the parameter.
- coc:service-name:region:account-id:resource-type:resource-path is the structure of resource permissions. The asterisk (*) indicates all permissions at this level. To add resource permissions, enter information in this format.
Parent topic: FAQs About Parameter Management
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.
The system is busy. Please try again later.
