Eugene Bekker

Sorry folks, I'm not a contributor to the ConfluencePS module. I've only contributed to JiraPS in the past, and that's fairly sporadic.

A sample of the byte stream: ``` [138,166,97,112,112,101,110,100,144,168,99,104,101,99,107,115,117,109,192,176,99,111,109,112,117,116,101,95,99,104,101,99,107,115,117,109,163,109,100,53,167,99,111,110,116,101,110,116,217,39,84,104,105,115,32,105,115,32,99,111,110,116,101,110,116,32,102,114,111,109,32,105,110,108,105,110,101,32,84,70,32,99,111,110,102,105,103,46,10,174,99,111,110,116,101,110,116,95,98,97,115,101,54,52,192,172,99,111,110,116,101,110,116,95,112,97,116,104,192,171,99,111,110,116,101,110,116,95,117,114,108,192,169,102,117,108,108,95,112,97,116,104,192,173,108,97,115,116,95,109,111,100,105,102,105,101,100,192,164,112,97,116,104,171,46,47,116,101,115,116,49,46,116,120,116] ```

For what it's worth, I think your session idea is great, it's very much like the [*Profile* concept](http://docs.aws.amazon.com/powershell/latest/userguide/specifying-your-aws-credentials.html) that's supported by the AWS PowerShell module for managing parameters to access...

I see you guys have consolidated all the PS modules for Atlassian products under one org -- I guess something like this change could become a common component of all...

So if I understand correctly, this will support having distinct connection profiles (i.e. server URL, credentials) in each PS session. But you would not be able to use different profiles...

Maybe add credentials to `JiraPS.Server` class? But then be sure to either securely store the file when exported (DataProtect) or use a SecureString for password (or just the PSCredential for...

Is there any reason to have distinct configs and associated cmdlets across the different AtlassianPS tools? Would it be better to just have a unified set, and all the tools...

@lipkau, that makes sense now -- sounds good. Just as you had questioned up above, I'm not sure if a `WebRequestSession` is *naturally* exportable, but you may be able to...

The problem with user _references_ when calling against Jira Cloud is that Jira Cloud forces _GDPR mode_ and all API calls that reference a user account have to use an...

Isn't the more functional approach in F# to pipe the value, such as `"foobar" |> ustring`?