Support different operations in policy engine #6

Closed
opened 2023-10-26 14:07:36 +00:00 by fyrchik · 2 comments
Owner

Currently the operation is just sting.

  1. We need to document the format. It could be similar to AWS arn, but I'd prefer more concise option.
  2. Operations in binary format could be just numbers (policy engine defined in enum).
  3. *to be extensible, consider having some kind of a union (numbers for well-known s3 and native operations, strings as an extended option).
Currently the operation is just sting. 1. We need to document the format. It could be similar to AWS arn, but I'd prefer more concise option. 2. Operations in binary format could be just numbers (policy engine defined in enum). 3. *to be extensible, consider having some kind of a union (numbers for well-known s3 and native operations, strings as an extended option).
fyrchik added the
enhancement
discussion
labels 2023-10-26 14:13:16 +00:00
Member

We need to document the format. It could be similar to AWS arn, but I'd prefer more concise option.

Do we suppose that the format has been agreed after @dstepanov-yadro added schema? Also, s3 format is supported

Operations in binary format could be just numbers (policy engine defined in enum).

Are you talking about using named numbers for these consts like PutObject/GetObject etc. ?

> We need to document the format. It could be similar to AWS arn, but I'd prefer more concise option. Do we suppose that the format has been agreed after @dstepanov-yadro added [schema](https://git.frostfs.info/TrueCloudLab/policy-engine/src/branch/master/schema/native/consts.go)? Also, [s3](https://git.frostfs.info/TrueCloudLab/policy-engine/src/branch/master/schema/s3/consts.go) format is supported > Operations in binary format could be just numbers (policy engine defined in enum). Are you talking about using named numbers for [these consts](https://git.frostfs.info/TrueCloudLab/policy-engine/src/branch/master/schema/native/consts.go#L4) like PutObject/GetObject etc. ?
Author
Owner

Do we suppose that the format has been agreed

Yes.

Operations are defined and restricted according to schema. Using numbers for them is encoding/decoding optimizations, will do in a separate task if needed.

Closed via #19

> Do we suppose that the format has been agreed Yes. Operations are defined and restricted according to schema. Using numbers for them is encoding/decoding optimizations, will do in a separate task if needed. Closed via #19
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: TrueCloudLab/policy-engine#6
No description provided.