Versions Compared

Old Version 9

changes.mady.by.user Ravi Varma

Saved on

compared with

New Version Current

changes.mady.by.user Nisha Shantilal

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


Warning
titleDeprecation notice

Please note that Username and Password parameters are deprecated and will be removed on March 31, 2022. We recommend using profiles to access your data from remote locations.

Description

This article illustrates how to create a profile for use with the CSV Table and JSON Table macros using a URL.

Info

Before you begin:

  • Before you enter the URL for a repository, ensure that it complies with the REST standards published by GitHub or GitLab.
    • Click here for more information on REST Pattern for GitLab.
    • Click here for more information on REST Pattern for GitHub.
  • Know what is a complete URL. A typical path for the raw file on GitLab looks like:
    /projects/:id/repository/files/:file_path/raw
  • Since the host address begins with:
     https://gitlab.com/api/v4
  • The complete URL, in this example, looks like: 
 https://gitlab.com/api/v4/projects/:id/repository/files/:file_path/raw?ref=master
  • For illustrative purposes, we have used a public Bitbucket public repository. The process for adding a profile and using it in macros remains the same for other repositories and external sources.
  • Verify that the URL conforms to the Confluence Whitelist; provided, whitelisting is enabled in Configuration settings.


There are three ways to work with URLs where you can use:

Info

The examples on this page use the CSV Table macro. Refer to the JSON Table macro documentation to know more about the macro's parameters relevant to profiles.

...