Skip to content

Conversation

@danielrbradley
Copy link
Contributor

Fixes #2839

The Migrate.VmUptimeArgs type is incompatible between 2019-10-01 and 2023-03-15 as the property HoursPerDay changed from a number to an integer, which is a breaking change. To avoid this, we exclude pulling the new AssessmentOperation resource into the default version.

To investigate the issue, I edited the flow so we still return and output the calculated versions on a failure so we can see what new resources are being added at what version.

This allows us to see what's changed in the version selection when schema generation starts to fail.
Migrate.AssessmentOperation references the type VmUptimeResponse already defined by a previous API version, but which changes a property hoursPerDay from being a number to an integer which is a breaking change.
@danielrbradley danielrbradley self-assigned this Oct 23, 2023
@github-actions
Copy link

Does the PR have any schema changes?

Looking good! No breaking changes found.
No new resources/functions.

@danielrbradley danielrbradley merged commit 91545a9 into master Oct 24, 2023
@danielrbradley danielrbradley deleted the upgrade-specs branch October 24, 2023 09:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Workflow failure: nightly-sdk-generation

3 participants