Update Dev branch with changes to Master #44
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
With the release of API v1.8.0, a new Passwords endpoint was added. This update uncovers that endpoint in the PowerShell module with the addition of the following functions: - `New-ITGluePasswords` - `Get-ITGluePasswords` - `Set-ITGluePasswords` Release notes for the Passwords api are available [here](https://kb.itglue.com/hc/en-us/articles/360001797531-Release-Note s-1-8-0-API). —————— The Module Version was also updated to reflect the API version it supports.
API endpoints have been added for deployments in the EU datacenter. This update uncovers the ability to use the EU API links by use of a `-data_center` (or `-dc`) option on the `Add-ITGlueBaseURI` function. This optional argument takes `EU` and `US` as options, however the US datacenter is still kept as the default even if no arguments are given. — HTTPS is also set by default for both the US and EU data centers.
Most endpoints (especially Index/Show, and Update) now allow for expanded filtering capabilities. This updated exposes those new capabilities as command parameters.
Fixed a bug that was pointed out that caused incorrect data to be returned from the `Get-ITGlueConfigurations’ function.
All resources now match the current API spec given at https://api.itglue.com/developer. This includes enhanced bulk update, bulk destroy, and filtering capabilities. Thanks to @TheMattCollins0 for changes to make adding an API key via command line easier.
This reverts commit 6c8f31e.
This reverts commit ead9f25.
…pper into development Syncing with current IT Glue Development Branch
* Update development branch with current proposed updates (#22) * Add Support for Passwords API With the release of API v1.8.0, a new Passwords endpoint was added. This update uncovers that endpoint in the PowerShell module with the addition of the following functions: - `New-ITGluePasswords` - `Get-ITGluePasswords` - `Set-ITGluePasswords` Release notes for the Passwords api are available [here](https://kb.itglue.com/hc/en-us/articles/360001797531-Release-Note s-1-8-0-API). —————— The Module Version was also updated to reflect the API version it supports. * Add support for EU API endpoints API endpoints have been added for deployments in the EU datacenter. This update uncovers the ability to use the EU API links by use of a `-data_center` (or `-dc`) option on the `Add-ITGlueBaseURI` function. This optional argument takes `EU` and `US` as options, however the US datacenter is still kept as the default even if no arguments are given. — HTTPS is also set by default for both the US and EU data centers. * Added enhanced filtering capability Most endpoints (especially Index/Show, and Update) now allow for expanded filtering capabilities. This updated exposes those new capabilities as command parameters. * Fixed Configurations Return Data Fixed a bug that was pointed out that caused incorrect data to be returned from the `Get-ITGlueConfigurations’ function. * Compatability Update All resources now match the current API spec given at https://api.itglue.com/developer. This includes enhanced bulk update, bulk destroy, and filtering capabilities. Thanks to @TheMattCollins0 for changes to make adding an API key via command line easier. * Added file to resolve Import-Module HRESULT: 0x8013104 * Support Nested Relationships Route for Show * Update Documents in Development branch (#25) * Markdown formatting edits and update doc for additional commands * Markdown formatting edits * Update to Current API Standards This update overhauls all endpoints to bring them current with the IT Glue API. Any and all filtering, options, and endpoints are covered. :warning: This is a **breaking** update. In order to better match the API docs that IT Glue presents at https://api.itglue.com/development, the `$data` input taken for module functions will *only* consist of the information present in the `data` array, rather than requiring what was effectively a `$body` request with a data array nested as a value. Some other styalistic choices were propogated throughout the code as well. For example, the `-important` parameter that some functions support now is a boolean. You no longer have to pass `0` or `1`, but can also pass `$true`, `$false`, or any other PowerShell boolean equivalent. * Minor ITGlueAPI.psd1 file edits (#27) * Markdown formatting edits and update doc for additional commands * Markdown formatting edits * Intial check in of basic tests for the module * Expanded testing * Minor edits * Revert "Expanded testing" This reverts commit 6c8f31e. * Revert "Intial check in of basic tests for the module" This reverts commit ead9f25. * Update to 2.0.0 The module version has been updated to `2.0.0`. From now on, Semantic Versioning (https://semver.org) should be followed on the module. Given a version number MAJOR.MINOR.PATCH, increment the: MAJOR version when you make incompatible API changes, MINOR version when you add functionality in a backwards-compatible manner, and PATCH version when you make backwards-compatible bug fixes. * Implement Error Handling on REST Headers This implements the fix suggested by @ecspresso (thanks!!) and closes #29. Co-Authored-By: Emile <[email protected]>
Fix Flex Asset Parameter Set
* Add Support for Passwords API With the release of API v1.8.0, a new Passwords endpoint was added. This update uncovers that endpoint in the PowerShell module with the addition of the following functions: - `New-ITGluePasswords` - `Get-ITGluePasswords` - `Set-ITGluePasswords` Release notes for the Passwords api are available [here](https://kb.itglue.com/hc/en-us/articles/360001797531-Release-Note s-1-8-0-API). —————— The Module Version was also updated to reflect the API version it supports. * Add support for EU API endpoints API endpoints have been added for deployments in the EU datacenter. This update uncovers the ability to use the EU API links by use of a `-data_center` (or `-dc`) option on the `Add-ITGlueBaseURI` function. This optional argument takes `EU` and `US` as options, however the US datacenter is still kept as the default even if no arguments are given. — HTTPS is also set by default for both the US and EU data centers. * Added enhanced filtering capability Most endpoints (especially Index/Show, and Update) now allow for expanded filtering capabilities. This updated exposes those new capabilities as command parameters. * Fixed Configurations Return Data Fixed a bug that was pointed out that caused incorrect data to be returned from the `Get-ITGlueConfigurations’ function. * Compatability Update All resources now match the current API spec given at https://api.itglue.com/developer. This includes enhanced bulk update, bulk destroy, and filtering capabilities. Thanks to @TheMattCollins0 for changes to make adding an API key via command line easier. * Added file to resolve Import-Module HRESULT: 0x8013104 * Sync'ing master with 2.0.0 release * Fix to remove variable correclty and minor spacing edits
Corrected Remove-ITGlueContacts paths
help about_Comparison_Operators
Bulk destroying configurations only uses the path /configurations, no nested route and not id in the parameter. Everything goes into the data object. Changed $resource_uri to reflect this (as pointed out in issue #65)
Bulk destroying configs - fixed invalid URI
added JSONDepth.ps1 for future use within the module
Revert "added JSONDepth.ps1 for future use within the module"
Null references and outputs updated
* Add Get-ITGlueDomains * Update ITGlueAPI.psd1 remove extra "s" * faster processing and cleaner method for nulling the output * Fix domains.ps1 parameter sets and resource_uri Co-authored-by: Caleb Albers <[email protected]>
* Add Get-ITGlueExpirations * Remove ValidatePattern * Add Get-ITGlueDomains * Update ITGlueAPI.psd1 remove extra "s" * faster processing and cleaner method for nulling the output * Update Expirations.ps1 Fixes some parameters Co-authored-by: Caleb Albers <[email protected]>
See #93 Suggestion to make Remove-ITGlueConfigurations behave like Remove-ITGlueFlexibleAssets. There is no endpoint in the API for single delete but the data structure is always the same so the wrapper can create that for us.
* Issues with Get-ITGlueConfigurationInterfaces Fix for #105: Made `$conf_id` mandatory for `index` path. Made `id` mandatory for `show` path and removed from `index` path. Added missing filter parameter for ip address. Changed default paramter set name to `index`. Changed `$resource_uri` to match index path. * Minor updates for params Fixes the updated_at sort and makes the resource_uri logic a bit more clear Co-authored-by: Caleb Albers <[email protected]>
* Added support for bulk create Added parameters and route to handle missing support for bulk creating new flexible assets. * Update param set name Co-authored-by: Caleb Albers <[email protected]>
* Add support for creating, updating, and removing attachments * faster processing and cleaner method for nulling the output * Little cleanup of [CmdletBinding()]
* Add support for creating, updating, and removing related items * faster processing and cleaner method for nulling the output * Little cleanup of [CmdletBinding()] * Update params to be idiomatic The other functions all use $id, so updated $related_items_id to match Co-authored-by: Caleb Albers <[email protected]>
These functions haven't been released to PS Gallery yet, so no breaking changes.
Had to implement this as a new parameter set, since psa_id requires psa_integration_type
* Update RMM integration type validation sets Adds: - auvik - logmein - meraki - syncro * Add PSA filtering to Configurations * Add support for Documents endpoint * Fix rmm and psa param sets * Update module manifest and tests
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #42