atlassianps/bitbucketps

PowerShell module to interact with Atlassian Bitbucket

AtlassianPS

bitbucketps's Issues

Attach resource to release

Make CI attach a zip of the release folder to the GitHub release

Add Travis CI

Remove Prefix from module

Make Prefix of Module interchangable (default value in psd1)
example in ConfluencePS

Support PowerShell Core

CI shall update homepage

Harmonize code with confluencePS and JiraPS

Set SupportsPaging

Functions that support paging should declare this in the CmdLetBindings (as in confluencePS)

Need prefix for functions

I know this was just removed, but it's badly needed. Jira is already using a prefix (Jira), but this module and the Confluence module are already in conflict. Both use Invoke-Method.

I propose we go back to BB, or BitB or something to differentiate this module from others.

Add Unit Tests

Improve Invoke-Method

Invoke-Method should be aligned with the sample in JiraPS (for basic layout) and ConfluencePS (for paging)

Compile module files into psm1

The Build task of the CI can modify the folder structure and manifest so that all functions are declared in the psm1 file

@martin9700: what do you think?

Question about Convertfrom-Json2

I was curious why you are using convertfrom-json2 instead of the built in convertfrom-json? In my testing of the module I cannot find a difference but maybe I'm missing something?

Thanks!

Branches API call does not expose ID number

Not sure if this is the right place to mention this, but! When calling the

$server/rest/api/1.0/projects/$ProjectKey/repos/$Repo/branches

API call, it does not expose the branch ID number, making it impossible to correlate commits to the branch. It looks like commits does expose the "parent ID" and I'm assuming this would be the ID number of the branch.

Alternative would be to add a branch search to the commits API call.

Decide how to handle cloud servers

Improve AppVeyor

• query REST for # of jobs
• Make last job run deploy task (not the rest)
• Make AppVeyor wait for Travis

Implement better session handling

Rest API version reference

I noticed in some examples in the API documentation that instead of using:

/rest/api/1.0/

this was used instead:

/rest/api/latest/

Is there any reason the latter shouldn't be used? Realistically will the URL ever change from 1.0?

Allow servers to be stored offline by object

Update CI environment

Migrate Documentation to Markdown and External Help

Description

In order to have a documentation that is easier to access, easier to edit and maintain, and more flexible, we shall use PlatyPS for the help of the function.
Discussion on this topic: AtlassianPS/AtlassianPS#1

Task

• Migrate all Comment Based Help to .md files in /docs

Import-Module MyAwesomeModule
New-MarkdownHelp -Module MyAwesomeModule -OutputFolder .\docs

• Edit the .md files (.EXAMPLE block can have more that 1 command in it)
• Create the about_<module>

New-MarkdownAboutHelp -OutputFolder C:\Test -AboutName

• Make AppVeyor generate the ExternalHelp file (.xml) when building

New-ExternalHelp -Path ".\docs" -OutputPath "out\platyPS\en-US"

• Remove the Comment Based Help from all functions in the module

Deploy to gallery

Support Tab-Completion for ServerName