Skip to content
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

Update deprecated endpoints in github/action_variables.go #3103

Closed
HariCharan-001 opened this issue Mar 15, 2024 · 4 comments
Closed

Update deprecated endpoints in github/action_variables.go #3103

HariCharan-001 opened this issue Mar 15, 2024 · 4 comments
Assignees

Comments

@HariCharan-001
Copy link
Contributor

HariCharan-001 commented Mar 15, 2024

$ ./script/metadata.sh update-go
could not find operation "GET /repositories/{repository_id}/environments/{environment_name}/variables" in openapi_operations.yaml
could not find operation "GET /repositories/{repository_id}/environments/{environment_name}/variables/{name}" in openapi_operations.yaml
could not find operation "POST /repositories/{repository_id}/environments/{environment_name}/variables" in openapi_operations.yaml
could not find operation "PATCH /repositories/{repository_id}/environments/{environment_name}/variables/{name}" in openapi_operations.yaml
could not find operation "DELETE /repositories/{repository_id}/environments/{environment_name}/variables/{name}" in openapi_operations.yaml

The official GitHub v3 API documentation has moved the endpoints above and now needs updating.

Detailed discussion around this can be traced to comments under #3102

@HariCharan-001
Copy link
Contributor Author

I'm working on a fix. Just giving a heads-up to avoid duplicate work.

@HariCharan-001
Copy link
Contributor Author

@gmlewis

Quick question on backward compatibility. Should we keep the older function signatures as they are and return an error "This endpoint has been moved, please use this new function instead" ?

I feel it's unnecessary, as the older API does not work anyway.

@gmlewis
Copy link
Collaborator

gmlewis commented Mar 16, 2024

If we can keep the same API and not break it, but just use the new endpoint URL, that would be ideal.

However, if the old API is broken anyway, and you need to break the API, then that's OK, just not ideal.

@HariCharan-001
Copy link
Contributor Author

The old API is broken anyway. We have to take a new parameter, github-userId, from the user to feed to the updated endpoint URL.

I raised a PR.

Also, it looks like this check has been failing for quite a few PRs recently, even some merged ones. Not sure why, bringing to your notice just in case.

Screenshot 2024-03-16 at 6 30 05 AM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants