Added support to enable contentSynchronisation for github issue 76

[AshutoshNirkhe]

Please note only enabled property of the contentSynchronisation JSON is added now.
This pull request will address the issue raised here -
#76

[atlassian-cla-bot]

Hooray! All contributors have signed the CLA.

[djsly]

thanks @AshutoshNirkhe !

@jamestoyer / @ttsangAtlassian can you guys review ?

[jamestoyer]

@djsly I can +1, but sadly I've no longer got maintainer privileges on this repo anymore 🙁

[djsly]

@jamestoyer thanks! do you know if this project is still alive within Atlassian ? I'm guessing you do not work for them anymore :(

[djsly]

@jamestoyer thanks! do you know if this project is still alive within Atlassian ? I'm guessing you do not work for them anymore :(

[ttsangAtlassian]

@djsly I'm still looking after from the Atlassian side however I'm working from Australia so our timezones might not match up.

[djsly]

Thanks for the merge. Would you have some insight on the expected release process for this provider ? It seems it hasn’t seen any updates for a while. :)

…

On Jun 3, 2020, at 7:44 PM, ttsangAtlassian ***@***.***> wrote:  Merged #77 into master. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[ttsangAtlassian]

We've been having some issues recently, I'll have a look at it. Just to set expectations, this provider is used actively internally by Atlassian but we are not providing active support for this outside of our needs. There may be some delays in solving issues.

[djsly]

Thanks. We are planning to use it more and more so as long as this isn’t a dead project we are open to continue with the contribution. Assuming we could expect some reasonable delay on the releases.

…

On Jun 3, 2020, at 8:22 PM, ttsangAtlassian ***@***.***> wrote:  We've been having some issues recently, I'll have a look at it. Just to set expectations, this provider is used actively internally by Atlassian but we are not providing active support for this outside of our needs. There may be some delays in solving issues. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.

[ttsangAtlassian]

@djsly @AshutoshNirkhe I've just cut a new release today that includes these changes. From now on it should be automatic

[djsly]

Great. Appreciate this! Happy to ditch our custom built provider

…

On Jun 11, 2020, at 9:48 PM, ttsangAtlassian ***@***.***> wrote:  @djsly @AshutoshNirkhe I've just cut a new release today that includes these changes. From now on it should be automatic — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or unsubscribe.