Repository navigation
Conversation
similar to key management, auth credentials for sources can be managed from within the resource. the resource is named after the source and can optionally be removed if needed. the configured credentials are only valid for their associated repository as the auth machine scope is set to the repo location.
|
Running CI tests for this PR here: #1296 |
|
Thank you for the PR @UiP9AV6Y ! I'm going to kick off some acceptance tests to get you some initial feedback. |
|
Acceptance Test Results: https://github.com/puppetlabs/puppetlabs-apt/actions/runs/37344670001?pr=1296 Looks like a full green across the board, except for Debian 11 which has acceptance test failures. These tests seem to match with nightly failures against the main branch, so not related to this PR but it looks like we probably need a separate PR to resolve that Debian 11 issue. Otherwise, this one looks good to go for review, tests are good! |
|
Quick update: I found #1292 and it has passing Debian 11 tests. It seems to resolve the issue there, so I've raised the priority on that one so we can get that reviewed and merged and resolve the testing issues for Debian 11. Then we'll be able to pull that down into this PR and redo the test suite and validate that it is full green even on Debian 11. |
|
After rebasing #1292 and rerunning tests, it also failed. Debian 11 appears to be an issue in the infra with provisioning, not something caused by this PR and not something fixed in other PRs. We are still considered 'green' and the Debian 11 issue needs to be resolved at infra level. |
Summary
similar to key management, auth credentials for sources can be managed from within the resource. the resource is named after the source and can optionally be removed if needed. the configured credentials are only valid for their associated repository as the auth machine scope is set to the repo location.
Checklist
puppet apply)