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

Some new functions and updated comments #256

Merged
merged 30 commits into from
Apr 12, 2021
Merged

Conversation

Stevio54
Copy link
Contributor

Hello Everyone, was hoping to have much higher coverage of IaaS at this point; However, here is what I have so far:

src/Functions/Public/iaas/Update-vRAvSphereFabricNetwork.ps1
src/Functions/Public/iaas/Update-vRAProject.ps1
src/Functions/Public/iaas/Update-vRAExternalNetworkIPRange.ps1
src/Functions/Public/iaas/Resize-vRAVirtualDisk.ps1
src/Functions/Public/iaas/New-vRANetworkProfile.ps1
src/Functions/Public/iaas/Get-vRAvSphereFabricNetwork.ps1

Each of those functions are new, and are included in this pull request. More work is ongoing.

Note: This branch is merged already with updates from "bugfix-update-connect-vraserver" so should be merged after that one.

@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

1 similar comment
@github-actions

This comment has been minimized.

Copy link
Contributor

@jonathanmedd jonathanmedd left a comment

Choose a reason for hiding this comment

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

Look good. Nice to seem some extra functions, including some Update-* now that we support the PATCH method.

src/Functions/Public/iaas/Get-vRAvSphereFabricNetwork.ps1 Outdated Show resolved Hide resolved
src/Functions/Public/iaas/New-vRANetworkProfile.ps1 Outdated Show resolved Hide resolved
@@ -214,3 +213,7 @@ function New-vRAVirtualDisk {

}
}

New-Alias -Name New-vRABlockDevice -Value New-vRAVirtualDisk
Export-ModuleMember -Alias * -Function *
Copy link
Contributor

Choose a reason for hiding this comment

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

@chelnak What do you think about this? Should we put any aliases into the module manifest rather than left in the code for a function?

If so, I guess we need to update the build process to get them in the right place automatically.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I will leave this one, but fix the other suggestions. I did this here because I was not aware of where else to do it. Is there a better procedure here? If so, I can just do that.

Copy link
Contributor

Choose a reason for hiding this comment

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

I think a "clean" way to handle aliases is to use an alias attribute:

    [CmdletBinding()]
    [Alias("New-vRABlockDevice")]
    PARAM ()

Then export them in the module manifest.

Thoughts?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I like that idea, seems easy to implement and use

Copy link
Contributor

Choose a reason for hiding this comment

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

I like it 👍🏻

@Stevio54 Can you update the function to implement the alias in that way and remove the Export-ModuleMember command. Then after merging, I'll update the build code in another branch to add any aliases implemented this way into the generated manifest.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Ok, on it

Copy link
Contributor Author

Choose a reason for hiding this comment

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

It is done.

@github-actions

This comment has been minimized.

1 similar comment
@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

1 similar comment
@github-actions

This comment has been minimized.

@Stevio54
Copy link
Contributor Author

Odd, there are build issues, let me work through these as well.

@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

@github-actions

This comment has been minimized.

1 similar comment
@github-actions

This comment has been minimized.

Copy link
Contributor

@jonathanmedd jonathanmedd left a comment

Choose a reason for hiding this comment

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

LGTM

@jonathanmedd jonathanmedd merged commit 949f9e0 into master Apr 12, 2021
@github-actions
Copy link

Unit Test Results

    1 files  ±0      1 suites  ±0   12s ⏱️ ±0s
149 tests ±0  149 ✔️ ±0  0 💤 ±0  0 ❌ ±0 

Results for commit 949f9e0. ± Comparison against base commit 949f9e0.

@jonathanmedd jonathanmedd deleted the feature-iaas-coverage branch April 12, 2021 14:37
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants