Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Resourceadm: use etag from resource registry in access list request #12813

Open
mgunnerud opened this issue May 15, 2024 · 0 comments · May be fixed by #12908
Open

Resourceadm: use etag from resource registry in access list request #12813

mgunnerud opened this issue May 15, 2024 · 0 comments · May be fixed by #12908
Assignees
Labels
area/resource-adm Issues related to resource administration kind/chore skip-releasenotes Issues that do not make sense to list in our release notes status/draft Status: When you create an issue before you have enough info to properly describe the issue.

Comments

@mgunnerud
Copy link
Contributor

Description

All accesslist requests in resource registry returns an etag (which is current version) as a response header. This etag should be sent back with request headers to handle errors when user try to update access lists simultaneously

Additional Information

No response

Tasks

No response

Acceptance Criterias

No response

@mgunnerud mgunnerud added status/draft Status: When you create an issue before you have enough info to properly describe the issue. skip-releasenotes Issues that do not make sense to list in our release notes kind/chore area/resource-adm Issues related to resource administration labels May 15, 2024
@mgunnerud mgunnerud self-assigned this Jun 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/resource-adm Issues related to resource administration kind/chore skip-releasenotes Issues that do not make sense to list in our release notes status/draft Status: When you create an issue before you have enough info to properly describe the issue.
Projects
Status: 👷In Progress
Development

Successfully merging a pull request may close this issue.

1 participant