Add job to maintain .repo-metadata information

[alicejli]

The information within the .repo-metdata.json file for each client library module is initially populated during creation of the new client library. After creation, there is not an automated way for the information to get updated.

The fields should come from the Cloud Drop yaml file and ideally there would be a process such that if the Cloud Drop yaml file is updated, the .repo-metadata.json file is also updated.

Many of the fields are used in our external documentation. For instance on the library overview page, the product documentation URL is explicitly linked, and the Enable the API link is created from the api_shortname.

[suztomo]

there is not an automated way for the information to get updated.

Would you add any known problems that are caused by the staleness?

[suztomo]

if the Cloud Drop yaml file is updated

About that "if". Am I right that that YAML file is not updated?

[alicejli]

if the Cloud Drop yaml file is updated

About that "if". Am I right that that YAML file is not updated?

The YAML file should be maintained and updated by the service owner teams. To your point, they are not typically updated frequently, but they can change.

Currently the .repo-metadata.json file we generate based on the YAML file is not updated automatically after the initial client library creation.