Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Workload feature band fallback with rollback files #24545

Conversation

gkulin
Copy link
Member

@gkulin gkulin commented Mar 24, 2022

fixes #23402

@gkulin gkulin requested a review from a team March 29, 2022 23:44
@gkulin gkulin marked this pull request as ready for review March 29, 2022 23:44
Copy link
Member

@dsplaisted dsplaisted left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM.

We also need to handle uninstalling the old versions of manifests (especially when we downgrade). I've filed #24628 for that.

Also, I believe we are now in M2 approval mode, so don't merge this yet until we get signoff.

Comment on lines +394 to +395
// TODO: figure out how to differentiate between the feature band an advertising manifest is branded as and the feature band of the SDK
// it's advertised to
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Normally we avoid leaving TODO comments in the code when we merge. If there is follow-up work to do, it's better to track it in an issue than a code comment.

If there are no other changes, I'm OK with leaving this in so we don't have to reset the CI checks. I've made a note about this in #23403.

Dictionary<WorkloadId, WorkloadDefinition> workloads) in manifestsToUpdate)
{
foreach ((WorkloadId WorkloadId, WorkloadDefinition workloadDefinition) in
workloads)
{
if (installedWorkloads.Contains(new WorkloadId(WorkloadId.ToString())))
{
// TODO: Potentially show existing and new feature bands
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Another TODO which should ideally be removed.

packInstaller.InstalledManifests[0].manifestId.Should().Be(manifestsToUpdate[0].manifestId);
packInstaller.InstalledManifests[0].manifestVersion.Should().Be(manifestsToUpdate[0].newVersion);
packInstaller.InstalledManifests[0].sdkFeatureBand.Should().Be(new SdkFeatureBand(newSdkFeatureBand));
packInstaller.InstalledManifests[0].offlineCache.Should().Be(null);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should ideally also check the existingVersion and existingFeatureBand.

Comment on lines +402 to +404
packInstaller.InstalledManifests[0].sdkFeatureBand.Should().Be(new SdkFeatureBand("6.0.100"));
packInstaller.InstalledManifests[1].sdkFeatureBand.Should().Be(new SdkFeatureBand("6.0.300"));
packInstaller.InstalledManifests[2].sdkFeatureBand.Should().Be(new SdkFeatureBand("6.0.100"));
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It would be a good idea to also check the existingFeatureBand for each manifest update.

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

Successfully merging this pull request may close these issues.

2 participants