Currently, the "golden path" for a user to find their library's assets is to:
Open their assets.json file
Manually go to the repository denoted by the AssetsRepo
Manually select the repo tag denoted by the Tag
Instead, we can provide a direct link to the repo tag and eliminate steps 2 and 3 by using currently-available information. For example, the assets.json file for Python's azure-keyvault-secrets currently looks like:
Currently, the "golden path" for a user to find their library's assets is to:
assets.json
fileAssetsRepo
Tag
Instead, we can provide a direct link to the repo tag and eliminate steps 2 and 3 by using currently-available information. For example, the
assets.json
file for Python'sazure-keyvault-secrets
currently looks like:By using the
AssetsRepo
andTag
fields, we can generate a direct link to the tag withand in the example above's case, add an extra field: