Skip to content

Update deprecated endpoints in github/action_variables.go #3103

Closed

Description

@HariCharanK
$ ./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

Activity

  1. HariCharanK commented on Mar 15, 2024

    @HariCharanK
    ContributorAuthor

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

  2. HariCharanK commented on Mar 16, 2024

    @HariCharanK
    ContributorAuthor

    @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.

  3. gmlewis commented on Mar 16, 2024

    @gmlewis
    Collaborator

    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.

  4. HariCharanK commented on Mar 16, 2024

    @HariCharanK
    ContributorAuthor

    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
  5. added a commit that references this issue on Mar 28, 2024
    8c1032a
  6. added a commit that references this issue on Jun 28, 2026
    c1a7023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions