Skip to content

Intune powershell Cmdlets module #1328

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

Merged
merged 107 commits into from
Dec 4, 2015
Merged

Intune powershell Cmdlets module #1328

merged 107 commits into from
Dec 4, 2015

Conversation

rnikhilkumar
Copy link
Contributor

Changes include

  1. Intune PS module
  2. Unit tests and Scenario test for it.

rnikhilkumar and others added 30 commits October 9, 2015 17:12
…hell into dev

Conflicts:
	src/ResourceManager/Intune/Commands.Intune/Commands.Intune.csproj
	src/ResourceManager/Intune/Commands.Intune/SwaggerManifest/2015-01-05/IntuneSwaggerManifest.json
// You can specify all the values or you can default the Build and Revision Numbers
// by using the '*' as shown below:
// [assembly: AssemblyVersion("1.0.*")]
[assembly: AssemblyVersion("1.0.0.0")]
Copy link
Member

Choose a reason for hiding this comment

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

These should both match the module version (1.0.1)

@markcowl
Copy link
Member

markcowl commented Dec 3, 2015

@rnikhilkumar Please fix the version issues.

The feedback I added on individual cmdlets applies across the board to many cmdlets - (1) OutputType should reflect the actual OutputType, (2) Only use ConfirmAction and Force on remove/update cmdlets, (3) You MUST NOT write messages to the output stream, (4) Your cmdlets would benefit from consolidating the different application types into a single add, get, and remove cmdlets where the user can specify the application type. These are usability issues that you will get negative feedback on from PowerShell users, but it is your call whether to fix these immediately (you have a day or two), or hold off for the next release.

@jianghaolu
Copy link
Contributor


internal static void InitializeEnvironment()
{
Environment.SetEnvironmentVariable("AZURE_TEST_MODE", "Playback");
Copy link
Member

Choose a reason for hiding this comment

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

@rnikhilkumar Please remove this - this will; prevent you from recording tests without help. This can wait until after the release, however.

@markcowl
Copy link
Member

markcowl commented Dec 4, 2015

@rnikhilkumar some changes which can be addressed next release. It looks like you have an app.config in your test project that needs to be removed (casuing failure). Once this is fixed and the builds pass, lgtm.

@markcowl
Copy link
Member

markcowl commented Dec 4, 2015

@jianghaolu
Copy link
Contributor

@vrmurthy01 Please finalize your pull request asap if you want to include this in the 1.1.0 release.

@jianghaolu
Copy link
Contributor

jianghaolu added a commit that referenced this pull request Dec 4, 2015
Intune powershell Cmdlets module
@jianghaolu jianghaolu merged commit 1c58d60 into Azure:dev Dec 4, 2015
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.

9 participants