Changes to enable module use within an Azure DevOps pipeline - #34
Changes to enable module use within an Azure DevOps pipeline#34whiteken wants to merge 2 commits into
Conversation
|
I'm not exactly sure what you're trying to accomplish. I've made the changes to remove the Throw error in PR #35. |
mkellerman
left a comment
There was a problem hiding this comment.
Need more information as to why this is done this way. Let's chat on Slack/Discord. Do you have access to the PowerShell Slack/Discord group? There is a #pstwitterapi channel.
|
@whiteken havent heard back... |
|
@mkellerman Please accept sincere apologies for total radio silence, I have to admit I completely forgot about this until a note from github on the last update this morning. "How is anyone supposed to know that this ArgumentList $true is to allow the usage of a config file?" is completely fair point. In the end (if I remember correctly) I forked and made those changes privately but they were pretty specific to my issue. Thanks for looking into it. |
For issues #32 and #33
If this PR is accepted, the -ArgumentList parameter is configured to look for $true which will introduce some changes designed for Azure DevOps build agents.
Command:
Import-Module PSTwitterAPI -ArgumentList $true -Force -Scope Local -Verbose
This will change current default module behaviour so that:
This will enable a successful module import from PSGallery during Azure DevOps pipeline release
If the ArgumentList parameter is not supplied on module load then no change is introduced.
(Sorry about the version number - but at least 0.0.8 is still a 00 agent - https://en.wikipedia.org/wiki/00_Agent)