-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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(galaxy-ansible): Switching from v2 api version to v3 #24947
Conversation
7f2c448
to
9bf341e
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please test against a public/demo repo to verify it all works as expected
@@ -36,7 +36,7 @@ export class GalaxyCollectionDatasource extends Datasource { | |||
const [namespace, projectName] = packageName.split('.'); | |||
|
|||
// TODO: types (#22198) | |||
const baseUrl = `${registryUrl}api/v2/collections/${namespace}/${projectName}/`; | |||
const baseUrl = `${registryUrl}api/v3/collections/${namespace}/${projectName}/`; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are you sure this is a fix
type PR? Switching to a new API may be a breaking change.
I guess at the very least this kind of change should go in a feat:
type PR, so it's not mingled with "real patches"?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I agree this should be a feat
.
Also is v3 really returning the exact same response on the same sub path?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for your feedback. Will change it to feat.
@secustor I've started to check it and the response is probably different. I don't know typescript enough to understand the errors it throws.
In any case, the v2 version is broken.
The following error is raised. No idea how to start debugging it. Would appreciate some help.
|
9bf341e
to
8d328a6
Compare
I think it's far more complicated than search/replace v2 to v3, we need to plan it in an issue first |
Created feature request: #24981 |
Changes
Context
Documentation (please check one with an [x])
How I've tested my work (please select one)
I have verified these changes via: