Skip to content

Programmatically Consumable Metadata about clients #3350

New issue
New issue
Closed
Closed
Programmatically Consumable Metadata about clients#3350
Assignees
sduskis
Labels
type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.

Description

@elharo
elharo
opened on Jun 6, 2018

Cloud Tools for Java has been maintaining a JSON file with info about the client libraries that we can consume in our products:

https://github.com/GoogleCloudPlatform/appengine-plugins-core/blob/master/src/main/resources/com/google/cloud/tools/libraries/libraries.json

We also have Java code for consuming and validating this file.

Any interest in moving this into google-cloud-java so everyone can use it and it stays in sync with releases?

Activity

  1. yihanzhen
    added
    type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.
    documentation
    priority: p2Moderately-important priority. Fix may not be included in next release.
    on Jun 6, 2018

  2. andreamlin commented on Jun 6, 2018

    @andreamlin
    andreamlin
    on Jun 6, 2018
    Contributor

    Are the existing pom.xmls sufficient?

  3. garrettjonesgoogle commented on Jun 6, 2018

    @garrettjonesgoogle
    garrettjonesgoogle
    on Jun 6, 2018
    Contributor

    We definitely wouldn't want to manually maintain that - it looks like it reflects data that is present in various places:

    1. versions.txt (maven coordinates)
    2. Derivable from versions in versions.txt (launchStage)
    3. service config (name, serviceName)
    4. README.md files (transport)
    5. ??? (serviceRoles)

    If your concern is the effort to manually maintain it yourself, then I can definitely see why you want to figure out an alternative. Maybe we should figure out how to make all of the datapoints programmatically accessible, so that it is easy to write a script to generate this. It wouldn't necessarily have to live in google-cloud-java; another repo could be set up to automatically regenerate when a new version of google-cloud-java is released.

    TL;DR I suggest we step back and design a solution instead of just moving it.

  4. elharo commented on Jun 6, 2018

    @elharo
    elharo
    on Jun 6, 2018
    ContributorAuthor

    We're not wedded to the current format. We just need some reasonable means of feeding this info into out tools.

  5. sduskis
    added
    type: docsImprovement to the documentation for an API.
    and removed
    priority: p2Moderately-important priority. Fix may not be included in next release.
    type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.
    type: docsImprovement to the documentation for an API.
    on Oct 9, 2018
  6. chingor13
    removed
    documentation
    type: docsImprovement to the documentation for an API.
    on Dec 3, 2018

  7. sduskis commented on Jun 11, 2019

    @sduskis
    sduskis
    on Jun 11, 2019
    Contributor

    This is something to work on offline if this is still relevant.

  8. sduskis
    closed this as completedon Jun 11, 2019
  9. JustinBeckwith
    assigned
    sduskis
    on Feb 1, 2021
  10. chingor13
    added 2 commits that reference this issue on Mar 24, 2026

    chore(main): release 6.76.0 (#3350)

    e39cbbd

    chore: mpu client preview merge train

    d0ebfd9
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

type: feature request‘Nice-to-have’ improvement, new feature or different behavior or design.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions