status: Introduce CONTAINER_ACCESS_DENIED
status #40
No reviewers
Labels
No labels
P0
P1
P2
P3
good first issue
triage
Infrastructure
blocked
bug
config
discussion
documentation
duplicate
enhancement
go
help wanted
internal
invalid
kludge
observability
perfomance
question
refactoring
wontfix
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: TrueCloudLab/frostfs-api#40
Loading…
Reference in a new issue
No description provided.
Delete branch "aarifullin/frostfs-api:feat/cnt_access_denied_status"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
The introduced
CONTAINER_ACCESS_DENIED
can be used by APE middleware check in container service.8739dd1070
tof574a7a85a
@ -135,1 +135,4 @@
EACL_NOT_FOUND = 1;
// [**3074**] Container access denied.
CONTAINER_ACCESS_DENIED = 2;
It also needs to be mentions in all RPCs, where it could be returned.
See object/service.proto for an example.
Fixed. Also, I have regenerated
md
s but it seems I use another version ofprotoc-gen-doc
plugin and the docs are reformatted. Is it critical?f574a7a85a
toe1e2713eb7
@ -26,1 +26,3 @@
// - Common failures (SECTION_FAILURE_COMMON).
// - Common failures (SECTION_FAILURE_COMMON);
// - **CONTAINER_ACCESS_DENIED** (3074, SECTION_CONTAINER): \
// container write access denied.
Maybe
container cerate access denied.
?Good point. Fixed
e1e2713eb7
to18de104072
18de104072
to07eb6a438c