We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Example on STAGE origins (not caching involved):
bundle is set on main-workspace (via permissions repo)
bundle
main-workspace
$ http "https://remote-settings.allizom.org/v1/buckets/main-workspace/collections/search-categorization/changeset?_expected=123456" "Authorization: $BEARER" | jq .metadata.attachment { "bundle": true, "enabled": true, "required": false }
Latest signature was 6 days ago:
$ http "https://remote-settings.allizom.org/v1/buckets/main-workspace/collections/search-categorization/changeset?_expected=123456" "Authorization: $BEARER" | jq .metadata.last_signature_date "2024-08-21T00:00:13.640960+00:00"
And the flag was added on the workspace collection 3 weeks ago.
So the bundle flag should be present in the main-preview and main collections, but it's not:
main-preview
main
$ http "https://remote-settings.allizom.org/v1/buckets/main-preview/collections/search-categorization/changeset?_expected=123456" "Authorization: $BEARER" | jq .metadata.attachment { "enabled": true, "required": false }
$ http "https://remote-settings.allizom.org/v1/buckets/main/collections/search-categorization/changeset?_expected=123456" "Authorization: $BEARER" | jq .metadata.attachment { "enabled": true, "required": false }
Using admin superpowers, let's trigger a signature refresh:
$ echo '{"data": {"status": "to-resign"}}' | http PATCH https://remote-settings.allizom.org/v1/buckets/main-workspace/collections/search-categorization --auth admin:$ADMINPASS_STAGE
The signature was refreshed as expected:
$ http "https://remote-settings.allizom.org/v1/buckets/main-workspace/collections/search-categorization/changeset?_expected=123456" "Authorization: $BEARER" | jq .metadata.last_signature_date "2024-08-27T18:19:07.910344+00:00"
But the bundle flag was not copied:
$ http "https://remote-settings.allizom.org/v1/buckets/main-preview/collections/search-categorization/changeset?_expected=123456789" "Authorization: $BEARER" | jq .metadata.attachment { "enabled": true, "required": false }
$ http "https://remote-settings.allizom.org/v1/buckets/main/collections/search-categorization/changeset?_expected=123456789" "Authorization: $BEARER" | jq .metadata.attachment { "enabled": true, "required": false }
This contradicts our unit tests:
remote-settings/kinto-remote-settings/tests/signer/test_updater.py
Lines 157 to 167 in f97cd84
Related:
build_bundles
The text was updated successfully, but these errors were encountered:
Fix #655: propagate fields of collection metadata on signature refresh
0ca2d5a
1e87f03
38cbd61
Fix #655: propagate fields of collection metadata on signature refre…
37421f5
…sh (#659) * Fix #655: propagate fields of collection metadata on signature refresh
Successfully merging a pull request may close this issue.
Example on STAGE origins (not caching involved):
bundle
is set onmain-workspace
(via permissions repo)Latest signature was 6 days ago:
And the flag was added on the workspace collection 3 weeks ago.
So the
bundle
flag should be present in themain-preview
andmain
collections, but it's not:Using admin superpowers, let's trigger a signature refresh:
The signature was refreshed as expected:
But the
bundle
flag was not copied:This contradicts our unit tests:
remote-settings/kinto-remote-settings/tests/signer/test_updater.py
Lines 157 to 167 in f97cd84
Related:
build_bundles
idempotence mozilla-services/remote-settings-lambdas#1488The text was updated successfully, but these errors were encountered: