You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To this point we've taken an ad-hoc approach to version updates of supported ASO resources, bringing in the new versions when users request.
We think there's merit in investigating how we might create a report to identify when the latest version included in ASO is significantly out of date. With the azure-rest-api-specs repo available as a submodule, we have the information available to do a cross check as a pipeline stage of the generator.
Initial thoughts (from a brainstorm during our weekly sync):
List all available newer versions
Define a threshold (say, 1 year) and highlight any resource where the newest stable version is more than that threshold newer than the latest stable version supported by ASO.
Define a second threshold (say, 9 months) and do the same highlighting, but for preview versions
We don't necessarily want to pull in every version (given we have hard CRD size limits we'll hit sooner or later)
The text was updated successfully, but these errors were encountered:
To this point we've taken an ad-hoc approach to version updates of supported ASO resources, bringing in the new versions when users request.
We think there's merit in investigating how we might create a report to identify when the latest version included in ASO is significantly out of date. With the
azure-rest-api-specs
repo available as a submodule, we have the information available to do a cross check as a pipeline stage of the generator.Initial thoughts (from a brainstorm during our weekly sync):
stable
version is more than that threshold newer than the lateststable
version supported by ASO.The text was updated successfully, but these errors were encountered: