-
Notifications
You must be signed in to change notification settings - Fork 0
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
feat: support multiple archives with "priority" field #12
feat: support multiple archives with "priority" field #12
Commits on Jul 9, 2024
-
feat: support multiple archives with "priority"
This commit adds support for fetching packages from multiple archives. It introduces a new field ``archives.<archive-name>.priority`` which takes in a signed integer and specifies the priority of a certain archive. This value is particularly useful when there are multiple archives. A package is fetched from the archive with highest priority regardless of the "default" archive, unless the slice definition file of that package specifies a particular archive using the "archive" field. Example chisel.yaml: format: v1 archives: foo: version: 22.04 components: [main, universe] priority: 20 public-keys: [..] bar: version: 22.04 components: [main] default: true priority: 10 public-keys: [..] In the above example, if a package exists in both of the archives, the package will be fetched from archive "foo" since it has higher priority. Note that, archive "bar" is the default. However, if in a particular package such as below, the "archive" field is used to specify a particular archive, that particular archive will be fetched from. package: test-package archive: bar slices: ... The above package will be fetched from archive "bar", regardless of priority. Reference: Specification RK018.
Configuration menu - View commit details
-
Copy full SHA for 0b00dc8 - Browse repository at this point
Copy the full SHA 0b00dc8View commit details
Commits on Jul 10, 2024
-
fix: ignore negative priority archives
If an archive has a negative priority, ignore it while choosing the best archive for a package. Unless, a package particularly asks for that particular archive with negative priority. In that case, that archive is chosen for the package.
Configuration menu - View commit details
-
Copy full SHA for 21973dc - Browse repository at this point
Copy the full SHA 21973dcView commit details
Commits on Jul 16, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 1c10089 - Browse repository at this point
Copy the full SHA 1c10089View commit details
Commits on Jul 25, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 1f4a454 - Browse repository at this point
Copy the full SHA 1f4a454View commit details
Commits on Jul 29, 2024
-
Configuration menu - View commit details
-
Copy full SHA for eef309d - Browse repository at this point
Copy the full SHA eef309dView commit details
Commits on Jul 30, 2024
-
Configuration menu - View commit details
-
Copy full SHA for ee7361e - Browse repository at this point
Copy the full SHA ee7361eView commit details
Commits on Sep 25, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 5e56edf - Browse repository at this point
Copy the full SHA 5e56edfView commit details
Commits on Sep 26, 2024
-
Configuration menu - View commit details
-
Copy full SHA for e85cd6b - Browse repository at this point
Copy the full SHA e85cd6bView commit details -
Configuration menu - View commit details
-
Copy full SHA for 3dd3183 - Browse repository at this point
Copy the full SHA 3dd3183View commit details -
Merge remote-tracking branch 'letfunny/chisel-db-create-manifest'
This commit merges the changes of 'feat: create manifest.wall'(canonical#142) into this branch. We need the changes of this commit to include the updated testing framework and changes. Co-authored-by: Alberto Carretero <[email protected]>
Configuration menu - View commit details
-
Copy full SHA for b85c182 - Browse repository at this point
Copy the full SHA b85c182View commit details -
Configuration menu - View commit details
-
Copy full SHA for 1cbac1a - Browse repository at this point
Copy the full SHA 1cbac1aView commit details -
Configuration menu - View commit details
-
Copy full SHA for c093dd0 - Browse repository at this point
Copy the full SHA c093dd0View commit details -
Configuration menu - View commit details
-
Copy full SHA for a98b4af - Browse repository at this point
Copy the full SHA a98b4afView commit details
Commits on Sep 27, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 000a244 - Browse repository at this point
Copy the full SHA 000a244View commit details -
Configuration menu - View commit details
-
Copy full SHA for 46a4a32 - Browse repository at this point
Copy the full SHA 46a4a32View commit details
Commits on Oct 2, 2024
-
Configuration menu - View commit details
-
Copy full SHA for 943ed01 - Browse repository at this point
Copy the full SHA 943ed01View commit details -
Configuration menu - View commit details
-
Copy full SHA for 5f6e78c - Browse repository at this point
Copy the full SHA 5f6e78cView commit details -
Configuration menu - View commit details
-
Copy full SHA for 0dc83e2 - Browse repository at this point
Copy the full SHA 0dc83e2View commit details -
Configuration menu - View commit details
-
Copy full SHA for 74b6bb3 - Browse repository at this point
Copy the full SHA 74b6bb3View commit details -
Configuration menu - View commit details
-
Copy full SHA for cb05332 - Browse repository at this point
Copy the full SHA cb05332View commit details -
fix: deprecate default archive in chisel.yaml
This commit deprecates the concept of default archive in chisel.yaml. In essence, it deprecates the "archives.<archive>.default" field from the chisel.yaml configurations. However, the field can still be present and it will be parsed but IGNORED. (See setup_test.go) DEPRECATED: "archives.<archive>.default" field in chisel.yaml.
Configuration menu - View commit details
-
Copy full SHA for 178dd51 - Browse repository at this point
Copy the full SHA 178dd51View commit details
Commits on Oct 3, 2024
-
test: remove remaining 'default: true' usage
There were some usage of the default field in archives left behind. This commit cleans them up.
Configuration menu - View commit details
-
Copy full SHA for fd75cc4 - Browse repository at this point
Copy the full SHA fd75cc4View commit details