7.0
7.0
Docs menu
MENU

Edit Access Control for Other Server Type

To edit access control, use the following request:

1
2

PUT /billing/buckets/:bucket_id/access_controls.xml
PUT /billing/buckets/:bucket_id/access_controls.json

XML Request Example

1

curl -i -X PUT http://onapp.test/billing/buckets/331/access_controls.xml -u user:userpass -H 'Accept: application/xml' -H 'Content-Type: application/xml' -d '<access_control><bucket_id>331</bucket_id><server_type>other</server_type><target_id>2</target_id><create_rate_card>false</create_rate_card><type>recipe_groups_resource</type><target_name>RecipeGroup1</target_name></access_control>'

JSON Request Example

1

curl -i -X PUT http://onapp.test/billing/buckets/331/access_controls.json -u user:userpass -H 'Accept: application/json' -H 'Content-Type: application/json' -d '{"access_control": {"bucket_id": 331, "server_type": "other", "target_id": 2, "type": "recipe_groups_resource", "target_name": "RecipeGroup1"}}'

Where:

bucket_id* - the ID of the bucket with which this access control is associated

server_type* - the server type this access control is applicable to, in this case, other

target_id - the ID of the resource added to the access control

type - the type of the resource for which configuration is set. For CDN resources, it can be one of the following values:

  • template_groups_resource

  • edge_groups_resource

  • recipe_groups_resource

  • service_addon_groups_resource

target_name - the name of the resource that is added to the access control. For example, it can be a label of a recipe group.