Uploaded image for project: 'Atlassian Ecosystem'
  1. Atlassian Ecosystem
  2. ECO-328

Allow wildcard prefix when defining baseUrls in Forge remotes

XMLWordPrintable

    • Our product teams collect and evaluate feedback from a number of different sources. To learn more about how we use customer feedback in the planning process, check out our new feature policy.

      When we define egress permissions directly, wildcard prefix ( * ) is accepted.

      permissions:
  external:
    fetch:
      backend:
        - '*.ingest.sentry.io'

      However, with forge remotes baseUrls cannot contain wildcard as prefix. So, the above manifest cannot be re-written like this.

      permissions:
  external:
    fetch:
      backend:
        - remote: remote-backend
remotes:
  - key: remote-backend
    baseUrl: "*.ingest.sentry.io"
    operations:
        - fetch

      Please add the ability to use wildcards with baseUrls in forge remotes.

      Workaround

      It's possible to add wildcard if we keep `https://` prefix like this.

      permissions:
  external:
    fetch:
      backend:
        - remote: remote-backend
remotes:
  - key: remote-backend
    baseUrl: "https://*.ingest.sentry.io"
    operations:
        - fetch

              Unassigned Unassigned
              2ed764d1efd7 Nashid Farhad
              Votes:
              4 Vote for this issue
              Watchers:
              9 Start watching this issue

                Created:
                Updated: