| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
Sorry, something went wrong.
There was a problem hiding this comment.
This PR updates the start-proxy action’s credential parsing/types so it can accept and forward future OIDC-based private registry authentication configurations (Azure/AWS/JFrog) to the Dependabot authentication proxy.
Changes:
Copilot reviewed 6 out of 6 changed files in this pull request and generated 4 comments.
Show a summary per file| File | Description |
|---|---|
| src/start-proxy/types.ts | Adds OIDC auth config types/guards and a new credentialToStr implementation for safe logging. |
| src/start-proxy/types.test.ts | New unit tests for credentialToStr across password/token/OIDC credential shapes. |
| src/start-proxy.ts | Adds getAuthConfig and updates credential validation/handling to propagate OIDC configs. |
| src/start-proxy.test.ts | Updates and expands tests for OIDC credential acceptance and validation behaviors. |
| lib/start-proxy-action.js | Generated build output (not reviewed). |
| CHANGELOG.md | Documents OIDC-registry config acceptance. |
src/start-proxy/types.ts:93
/** Decides whether `config` is an AWS OIDC configuration. */
export function isAWSConfig(config: Partial<AuthConfig>): config is AWSConfig {
// All of these properties are required.
const requiredProperties = [
"aws_region",
"account_id",
"role_name",
"domain",
"domain_owner",
];
for (const property of requiredProperties) {
if (!(property in config) || !isDefined(config[property])) {
return false;
}
}
return true;
}
src/start-proxy/types.ts:109
/** Decides whether `config` is a JFrog OIDC configuration. */
export function isJFrogConfig(
config: Partial<AuthConfig>,
): config is JFrogConfig {
return (
"jfrog_oidc_provider_name" in config &&
isDefined(config.jfrog_oidc_provider_name)
);
Sorry, something went wrong.
There was a problem hiding this comment.
A minor thing, otherwise lgtm!
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
The Dependabot team have been working on support for OIDC-based authentication in the Dependabot authentication proxy, which we also use to support private package registries in Default Setup.
This PR modifies the start-proxy action to accept such configurations and propagate them to the proxy. This will ensure that we are ready to support OIDC-based authentication when such configurations are available to us. This is not yet the case at the time of writing.
However, that should not block this PR from being merged, since we just perform validation that will allow such configurations to be propagated to the proxy in the future.
Notes for reviewers
Best reviewed commit-by-commit. See the internal issue for more context and references.
Risk assessment
For internal use only. Please select the risk level of this change:
Which use cases does this change impact?
Workflow types:
Products:
Environments:
How did/will you validate this change?
If something goes wrong after this change is released, what are the mitigation and rollback strategies?
How will you know if something goes wrong after this change is released?
Are there any special considerations for merging or releasing this change?
Merge / deployment checklist