Skip to content

Conversation

@MiYanni
Copy link
Contributor

@MiYanni MiYanni commented Nov 6, 2018

Description

This makes it so that Automation does not rely on the ResourceManager SDK directly. Instead, it uses our internal version of it. I've also made sure everything is using 1.9.1-preview of ResourceManager SDK (for those that do use it).

Checklist

…ceManager SDK to 1.9.1-preview for all modules/references.

<ItemGroup>
<PackageReference Include="Microsoft.Azure.Management.ResourceManager" Version="2.0.0-preview" />
<PackageReference Include="Microsoft.Azure.Management.ResourceManager" Version="1.9.1-preview" />
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't think we should downgrade the package in Resources.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The version was not upgraded in our repo; only in their branch. I aligned the version that we upgraded in our repo (from 1.9.0-preview to 1.9.1-preview). I changed this from 1.9.0-preview to 2.0.0-preview in a previous PR to fix their branch. But, now, I've gotten it to work without upgrading everyone to 2.0.0-preview.

<PackageReference Include="Microsoft.Azure.Management.Redis" Version="4.4.1" PrivateAssets="All" />
<PackageReference Include="Microsoft.Azure.Management.Relay" Version="2.0.2" PrivateAssets="All" />
<PackageReference Include="Microsoft.Azure.Management.ResourceManager" Version="2.0.0-preview" PrivateAssets="All" />
<PackageReference Include="Microsoft.Azure.Management.ResourceManager" Version="1.9.1-preview" PrivateAssets="All" />
Copy link
Contributor

Choose a reason for hiding this comment

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

Should we be downgrading this version?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

See above response.

<packages>
<package id="Microsoft.Azure.Management.Automation" version="3.4.0-preview" targetFramework="net452" />
<package id="Microsoft.Azure.Management.ResourceManager" version="2.0.0-preview" targetFramework="net452" />
<package id="Microsoft.Azure.Management.ResourceManager" version="1.9.1-preview" targetFramework="net452" />
Copy link
Contributor

Choose a reason for hiding this comment

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

Shouldn't we just remove this altogether?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yes, I'm less concerned about doing that since these files (all .config files) will be removed in 2 weeks anyway. I just flat changed all Management.ResourceManager references to the same version (to be consistent).

@MiYanni
Copy link
Contributor Author

MiYanni commented Nov 8, 2018

@MiYanni
Copy link
Contributor Author

MiYanni commented Nov 10, 2018

@MiYanni
Copy link
Contributor Author

MiYanni commented Nov 13, 2018

@maddieclayton This should be good-to-merge once the build completes successfully.

@maddieclayton maddieclayton removed their assignment Nov 13, 2018
@MiYanni MiYanni merged commit fae35bb into Azure:AzureRM.Automation Nov 13, 2018
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.

3 participants