Run builds on push to master branch
alexvanin
deleted branch feature/ci-push-to-master from potyarkin/frostfs-s3-gw
2024-11-18 11:41:34 +00:00
Execute CI on push to master
alexvanin
deleted branch feature/ci-push-to-master from potyarkin/frostfs-http-gw
2024-11-18 11:41:05 +00:00
Execute CI on push to master
Support secondary keys in FrostFSID contract
Could you describe the correct behaviour w.r.t to APE rules?
Consider Alice having primary key key_1
and secondary keys key_2
and key_3
.
Examples:
- Request is signed by
key_2
.…
6a28d9edbe
wip
eff0de43d5
[#538] Return headers with 304 Not Modified
fb00dff83b
[#540] Add md5 S3Tests compatability
d8f126b339
[#539] Fix listing v1 bookmark marker
7ab902d8d2
[#536] Add rule ID generation
Run builds on push to master branch
Would you like this behavior in frostfs-s3-gw only or across all of services team repos?
Let's do this across s3 and http gateways. Not sure we need schedule runs, on push should be enough.
Run builds on push to master branch
I am against "ff-only" merge strategy, because master breaks happen quite rarely, and ff-only is going to slow down merge process in my opinion.
Run builds on push to master branch
JSON bearer tokens in HTTP request headers
I think the size of the JSON was the issue last time we talked about it.
Since then allowImpesonate
flag was introduced, which provides very short bearer tokens.
On the other hand, bearer…