Skip to content
This repository was archived by the owner on Sep 14, 2026. It is now read-only.
This repository was archived by the owner on Sep 14, 2026. It is now read-only.

Cloud BOM should not include non-GA'd API's #470

Closed as not planned
Closed as not planned

Description

@lesv

Ideally, the Cloud BOM would not include unstable API's like the Healthcare and Jobs api's.

GoogleCloudPlatform/java-docs-samples#2577 shows where methods, fields and such change and BOM updates break samples.

  • accessapproval
  • billing-budgets
  • compute
  • datalabeling
  • dns
  • document-ai
  • errorreporting
  • irm
  • logging-logback
  • mediatranslation
  • memcache
  • monitoring-dashboard
  • phishingprotection
  • resourcemanager
  • servicedirectory
  • talent
  • grafeas

Activity

  1. added
    api: jobsIssues related to the Cloud Talent Solution Job Search API.
    on Apr 6, 2020
  2. danoscarmike commented on Apr 13, 2020

    @danoscarmike

    @lesv what do you recommend? I'm assuming we can't just delete them from pom.xml?

  3. lesv commented on Apr 13, 2020

    @lesv
    Author

    I think we should bump the major version, and delete them, yes. The fields change still change on non-GA'd api's. The purpose of BOM's is to keep things working for users, not to mess w/ their world.
    @chingor13

  4. chingor13 commented on Apr 13, 2020

    @chingor13
    Contributor

    We still need a way to help users use clients that are not yet marked 1.0.0

  5. lesv commented on Apr 13, 2020

    @lesv
    Author

    Why? They should just use it directly, the tag should be BETA or ALPHA, so it will remind them it's not supported. We are very clear everywhere else, if you want, we can release an beta-bom, but I don't think it's a good idea.

  6. added
    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.
    on Apr 13, 2020
  7. chingor13 commented on Apr 13, 2020

    @chingor13
    Contributor

    @elharo We need to decide how we want to handle non 1.0 clients

  8. chingor13 commented on Apr 20, 2020

    @chingor13
    Contributor

    After some internal discussion, the plan is to:

    • stop adding pre-1.0 libraries to the google-cloud-bom
    • Push pre-1.0 libraries towards 1.0 releases
    • Keep pre-1.0 libraries which will not be 1.0 as debt (possibly revisit when this library goes to 1.0 itself)
  9. added
    🚨This issue needs some love.
    and removed
    🚨This issue needs some love.
    on Jul 19, 2020
  10. added
    type: processA process-related concern. May include testing, release, or the like.
    and removed
    type: bugError or flaw in code with unintended results or allowing sub-optimal usage patterns.
    priority: p2Moderately-important priority. Fix may not be included in next release.
    on Oct 15, 2020
  11. assigned and unassigned on Jul 27, 2021
  12. suztomo commented on Dec 3, 2022

    @suztomo
    Member

    Update: We decided to include both GA and non-GA libraries in the BOM.

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

Metadata

Metadata

Assignees

Labels

api: jobsIssues related to the Cloud Talent Solution Job Search API.priority: p4type: processA process-related concern. May include testing, release, or the like.

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions