Uploaded image for project: 'Bitbucket Data Center'
  1. Bitbucket Data Center
  2. BSERV-13347

Document publicly options to fix ports for callback hooks

    XMLWordPrintable

Details

    • Suggestion
    • Resolution: Unresolved
    • None
    • Documentation (User)
    • None
    • We collect Bitbucket feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

    Description

      We have 3 callback hooks that listen on ports assigned dynamically on startup.
      Customers with restrictive firewalls need to pre-set them statically so they can add them to firewall allowlists. Currently, this is not documented in Configuration properties

      Can we add the following to this doc with relevant descriptions (might need devs to chip in for accuracy:

      hook.callback.socket.port=<port of choice>
git.hook.socket.port=<port of choice>
plugin.bitbucket-git.transcode.socket.port=<port of choice>

      Note - for git.hook-> I haven't confirmed when this was introduced. It was in a 7+ version

      Thanks!

      Attachments

        Activity

          People

            Unassigned Unassigned
            tathanassiadou Themis
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated: