@n8n-dev/n8n-nodes-lgtm 1.0.0

package/dist/nodes/Lgtm/resources/projects/index.js

@@ -0,0 +1,822 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.projectsDescription = void 0;
+exports.projectsDescription = [
+    {
+        "displayName": "Operation",
+        "name": "operation",
+        "type": "options",
+        "noDataExpression": true,
+        "displayOptions": {
+            "show": {
+                "resource": [
+                    "Projects"
+                ]
+            }
+        },
+        "options": [
+            {
+                "name": "Get Projects",
+                "value": "Get Projects",
+                "action": "List projects",
+                "description": "List all the projects the current user has authorization to view. \n\nA maximum of 100 projects are returned in each response. When further results are available, the response includes the URL you need to request the next page of results.\n\nUse the optional parameter, `limit`, to change the number of results reported in each response (range of 1—100). If you supply an invalid value for this  parameter, the default value of 100 is used.\n\nWhen more than one page of results is available, each response includes a `nextPageUrl` response parameter. You can use this URL to request the next page of results. The `nextPageUrl` includes an automatically generated `start` parameter, which specifies the projects to return in the next page of results.\n",
+                "routing": {
+                    "request": {
+                        "method": "GET",
+                        "url": "=/projects"
+                    }
+                }
+            },
+            {
+                "name": "Add Project",
+                "value": "Add Project",
+                "action": "Add a project to LGTM",
+                "description": "LGTM administrators can add a new project to LGTM by providing a repository URL. By default, LGTM tries to build and analyze the project in the same way as for projects added through the user interface. If at least one language is successfully analyzed, and the repository doesn't already exist on LGTM, a new project is created. If the project already exists but your API call triggers a successful analysis  of additional languages, LGTM adds those languages to the project.\n\nYou can configure how LGTM processes the project using query parameters to:\n  * Specify the languages to analyze.\n  * Create a new project in [sparse mode](https://help.semmle.com/lgtm-enterprise/user/help/analysis-faqs.html#what-is-sparse-analysis).\n  * Create a new project in [upload mode](https://help.semmle.com/lgtm-enterprise/user/help/analysis-faqs.html#what-is-upload-analysis) to analyze externally-generated databases. Each database represents a snapshot of the codebase. \n  Use this option when you want to upload databases that were generated by the CodeQL CLI (or the QL command-line tools).\n  The version of the command line used to generate the database\n  must be the same version as LGTM Enterprise. \n\nWith any of these options, you can also include an `lgtm.yml` in the body of the request to [customize extraction](https://lgtm.com/help/lgtm/customizing-code-extraction).\n",
+                "routing": {
+                    "request": {
+                        "method": "POST",
+                        "url": "=/projects"
+                    }
+                }
+            },
+            {
+                "name": "Delete Project",
+                "value": "Delete Project",
+                "action": "Delete project by numeric identifier",
+                "description": "Delete a project with a particular numeric project identifier.\nIn addition to access to the project, administrative access to LGTM or the LGTM Enterprise instance is required to delete projects.\n",
+                "routing": {
+                    "request": {
+                        "method": "DELETE",
+                        "url": "=/projects/{{$parameter[\"project-id\"]}}"
+                    }
+                }
+            },
+            {
+                "name": "Get Project",
+                "value": "Get Project",
+                "action": "Get project by numeric identifier",
+                "description": "Get the latest summary for a specific project using the numeric project identifier.\n\nTo find the LGTM identifier for a project, list all projects using the `/projects`  endpoint and look up the project by name. Alternatively, use the `/projects/{provider}/{org}/{name}` endpoint. If you have administration access, the project identifier is also displayed in  the administration page for the project.\n",
+                "routing": {
+                    "request": {
+                        "method": "GET",
+                        "url": "=/projects/{{$parameter[\"project-id\"]}}"
+                    }
+                }
+            },
+            {
+                "name": "Get Project Config",
+                "value": "Get Project Config",
+                "action": "Get configuration for a project identified by numeric identifier",
+                "description": "Get the latest configuration for a specific project using the numeric project identifier.",
+                "routing": {
+                    "request": {
+                        "method": "GET",
+                        "url": "=/projects/{{$parameter[\"project-id\"]}}/settings/analysis-configuration"
+                    }
+                }
+            },
+            {
+                "name": "Set Project Config",
+                "value": "Set Project Config",
+                "action": "Set the administrator configuration for a project identified by numeric identifier",
+                "description": "Set the administrator configuration for a specific project using the numeric project identifier.",
+                "routing": {
+                    "request": {
+                        "method": "PUT",
+                        "url": "=/projects/{{$parameter[\"project-id\"]}}/settings/analysis-configuration"
+                    }
+                }
+            },
+            {
+                "name": "Get Project By URL Identifier",
+                "value": "Get Project By URL Identifier",
+                "action": "Get project by URL identifier",
+                "description": "Get the latest summary for a specific project using the project's URL identifier `{provider}/{org}/{name}`.\n\nTo find the URL identifier for a project, view the project overview page in LGTM. The URL identifier follows after `/projects`. For example, for a project with the URL `https://lgtm.example.com/projects/g/apache/commons-io` the URL identifier is `g/apache/commons-io`. In the example, `g` represents the `provider` (repository host), `apache` is the `organization` and `commons-io` is the `name` of the repository.\n",
+                "routing": {
+                    "request": {
+                        "method": "GET",
+                        "url": "=/projects/{{$parameter[\"provider\"]}}/{{$parameter[\"org\"]}}/{{$parameter[\"name\"]}}"
+                    }
+                }
+            }
+        ],
+        "default": ""
+    },
+    {
+        "displayName": "GET /projects",
+        "name": "operation",
+        "type": "notice",
+        "typeOptions": {
+            "theme": "info"
+        },
+        "default": "",
+        "displayOptions": {
+            "show": {
+                "resource": [
+                    "Projects"
+                ],
+                "operation": [
+                    "Get Projects"
+                ]
+            }
+        }
+    },
+    {
+        "displayName": "Limit",
+        "name": "limit",
+        "description": "The maximum number of projects to return in each response (1-100).",
+        "default": 100,
+        "type": "number",
+        "routing": {
+            "send": {
+                "type": "query",
+                "property": "limit",
+                "value": "={{ $value }}",
+                "propertyInDotNotation": false
+            }
+        },
+        "displayOptions": {
+            "show": {
+                "resource": [
+                    "Projects"
+                ],
+                "operation": [
+                    "Get Projects"
+                ]
+            }
+        }
+    },
+    {
+        "displayName": "Start",
+        "name": "start",
+        "description": "An opaque identifier generated by the API.",
+        "default": "",
+        "type": "string",
+        "routing": {
+            "send": {
+                "type": "query",
+                "property": "start",
+                "value": "={{ $value }}",
+                "propertyInDotNotation": false
+            }
+        },
+        "displayOptions": {
+            "show": {
+                "resource": [
+                    "Projects"
+                ],
+                "operation": [
+                    "Get Projects"
+                ]
+            }
+        }
+    },
+    {
+        "displayName": "Bearer Token",
+        "name": "security_access_token",
+        "type": "string",
+        "default": "",
+        "description": "\n\nLGTM Enterprise users need to create and use an access token to authenticate with this API. This is optional for LGTM.com users unless they want to submit a CodeQL query for analysis of one or more projects, or to request the analysis of a patch or commit. LGTM.com users also need an access token to  check on the progress of long running tasks using the `/operations` endpoint.\nLog in to LGTM and use the **Create token** option in your Account settings page. For more detailed information, see [Authentication with the API](https://lgtm.com/help/lgtm/api/authentication-api) and [Managing access tokens](https://lgtm.com/help/lgtm/api/managing-access-tokens).\nIf you include an access token in the header of a request to the API  for data, it must have the scopes required by that endpoint. Access tokens are shown in the examples as: `Authorization: Bearer {access-token}`\n",
+        "required": false,
+        "routing": {
+            "request": {
+                "headers": {
+                    "Authorization": "={{ 'Bearer ' + $value }}"
+                }
+            }
+        },
+        "displayOptions": {
+            "show": {
+                "resource": [
+                    "Projects"
+                ],
+                "operation": [
+                    "Get Projects"
+                ]
+            }
+        }
+    },
+    {
+        "displayName": "POST /projects",
+        "name": "operation",
+        "type": "notice",
+        "typeOptions": {
+            "theme": "info"
+        },
+        "default": "",
+        "displayOptions": {
+            "show": {
+                "resource": [
+                    "Projects"
+                ],
+                "operation": [
+                    "Add Project"
+                ]
+            }
+        }
+    },
+    {
+        "displayName": "Repository",
+        "name": "repository",
+        "required": true,
+        "description": "The URL of the repository to analyze.\nLGTM tests this against the [repository providers](https://lgtm.com/admin/help/adding-repository-providers) defined for the system. If it doesn't match any of them, the request fails.",
+        "default": "",
+        "type": "string",
+        "routing": {
+            "send": {
+                "type": "query",
+                "property": "repository",
+                "value": "={{ $value }}",
+                "propertyInDotNotation": false
+            }
+        },
+        "displayOptions": {
+            "show": {
+                "resource": [
+                    "Projects"
+                ],
+                "operation": [
+                    "Add Project"
+                ]
+            }
+        }
+    },
+    {
+        "displayName": "Language",
+        "name": "language",
+        "description": "Optional, a [language code](https://lgtm.com/help/lgtm/analysis-faqs#which-languages-are-supported) to specify which language to analyze.\nTo request the analysis of more than one language, specify a query parameter for each language. By default, LGTM tries to analyze all supported languages.\n",
+        "default": "[\n  null\n]",
+        "type": "json",
+        "routing": {
+            "send": {
+                "type": "query",
+                "property": "language",
+                "value": "={{ $value }}",
+                "propertyInDotNotation": false
+            }
+        },
+        "displayOptions": {
+            "show": {
+                "resource": [
+                    "Projects"
+                ],
+                "operation": [
+                    "Add Project"
+                ]
+            }
+        }
+    },
+    {
+        "displayName": "Mode",
+        "name": "mode",
+        "description": "The analysis mode of the new project.\nWhen set to `full` all commits of the project are analyzed; when set to `sparse` the latest commit of the project is analyzed periodically; when set to `upload`,  no automatic analysis is performed, instead externally-generated databases should be uploaded.\nFor new projects the default value is `full`. The `mode` parameter cannot be used to change the analysis mode of existing projects. Therefore, for existing projects, it should either be left blank or set to match the analysis mode of the project.\n",
+        "default": "full",
+        "type": "options",
+        "options": [
+            {
+                "name": "Full",
+                "value": "full"
+            },
+            {
+                "name": "Sparse",
+                "value": "sparse"
+            },
+            {
+                "name": "Upload",
+                "value": "upload"
+            }
+        ],
+        "routing": {
+            "send": {
+                "type": "query",
+                "property": "mode",
+                "value": "={{ $value }}",
+                "propertyInDotNotation": false
+            }
+        },
+        "displayOptions": {
+            "show": {
+                "resource": [
+                    "Projects"
+                ],
+                "operation": [
+                    "Add Project"
+                ]
+            }
+        }
+    },
+    {
+        "displayName": "Commit",
+        "name": "commit",
+        "description": "Required when `mode=upload`, specify the identifier of the commit used to generate the database.",
+        "default": "",
+        "type": "string",
+        "routing": {
+            "send": {
+                "type": "query",
+                "property": "commit",
+                "value": "={{ $value }}",
+                "propertyInDotNotation": false
+            }
+        },
+        "displayOptions": {
+            "show": {
+                "resource": [
+                    "Projects"
+                ],
+                "operation": [
+                    "Add Project"
+                ]
+            }
+        }
+    },
+    {
+        "displayName": "Date",
+        "name": "date",
+        "description": "Optional when `mode=upload`, specify the date and time of the commit used to generate the database; defaults to the current time.",
+        "default": "",
+        "type": "string",
+        "routing": {
+            "send": {
+                "type": "query",
+                "property": "date",
+                "value": "={{ $value }}",
+                "propertyInDotNotation": false
+            }
+        },
+        "displayOptions": {
+            "show": {
+                "resource": [
+                    "Projects"
+                ],
+                "operation": [
+                    "Add Project"
+                ]
+            }
+        }
+    },
+    {
+        "displayName": "Worker Label",
+        "name": "worker-label",
+        "description": "Optional, any [labels](https://lgtm.com/admin/help/defining-worker-labels) required by workers to analyze this project. \nTo specify more than one label, repeat the query parameter.\n",
+        "default": "[\n  null\n]",
+        "type": "json",
+        "routing": {
+            "send": {
+                "type": "query",
+                "property": "worker-label",
+                "value": "={{ $value }}",
+                "propertyInDotNotation": false
+            }
+        },
+        "displayOptions": {
+            "show": {
+                "resource": [
+                    "Projects"
+                ],
+                "operation": [
+                    "Add Project"
+                ]
+            }
+        }
+    },
+    {
+        "displayName": "POST /projects<br/><br/>There's no body available for request, kindly use HTTP Request node to send body",
+        "name": "operation",
+        "type": "notice",
+        "default": "",
+        "displayOptions": {
+            "show": {
+                "resource": [
+                    "Projects"
+                ],
+                "operation": [
+                    "Add Project"
+                ]
+            }
+        }
+    },
+    {
+        "displayName": "Bearer Token",
+        "name": "security_access_token",
+        "type": "string",
+        "default": "",
+        "description": "\n\nLGTM Enterprise users need to create and use an access token to authenticate with this API. This is optional for LGTM.com users unless they want to submit a CodeQL query for analysis of one or more projects, or to request the analysis of a patch or commit. LGTM.com users also need an access token to  check on the progress of long running tasks using the `/operations` endpoint.\nLog in to LGTM and use the **Create token** option in your Account settings page. For more detailed information, see [Authentication with the API](https://lgtm.com/help/lgtm/api/authentication-api) and [Managing access tokens](https://lgtm.com/help/lgtm/api/managing-access-tokens).\nIf you include an access token in the header of a request to the API  for data, it must have the scopes required by that endpoint. Access tokens are shown in the examples as: `Authorization: Bearer {access-token}`\n",
+        "required": false,
+        "routing": {
+            "request": {
+                "headers": {
+                    "Authorization": "={{ 'Bearer ' + $value }}"
+                }
+            }
+        },
+        "displayOptions": {
+            "show": {
+                "resource": [
+                    "Projects"
+                ],
+                "operation": [
+                    "Add Project"
+                ]
+            }
+        }
+    },
+    {
+        "displayName": "DELETE /projects/{project-id}",
+        "name": "operation",
+        "type": "notice",
+        "typeOptions": {
+            "theme": "info"
+        },
+        "default": "",
+        "displayOptions": {
+            "show": {
+                "resource": [
+                    "Projects"
+                ],
+                "operation": [
+                    "Delete Project"
+                ]
+            }
+        }
+    },
+    {
+        "displayName": "Project ID",
+        "name": "project-id",
+        "required": true,
+        "description": "The numeric project identifier",
+        "default": 0,
+        "type": "number",
+        "displayOptions": {
+            "show": {
+                "resource": [
+                    "Projects"
+                ],
+                "operation": [
+                    "Delete Project"
+                ]
+            }
+        }
+    },
+    {
+        "displayName": "Bearer Token",
+        "name": "security_access_token",
+        "type": "string",
+        "default": "",
+        "description": "\n\nLGTM Enterprise users need to create and use an access token to authenticate with this API. This is optional for LGTM.com users unless they want to submit a CodeQL query for analysis of one or more projects, or to request the analysis of a patch or commit. LGTM.com users also need an access token to  check on the progress of long running tasks using the `/operations` endpoint.\nLog in to LGTM and use the **Create token** option in your Account settings page. For more detailed information, see [Authentication with the API](https://lgtm.com/help/lgtm/api/authentication-api) and [Managing access tokens](https://lgtm.com/help/lgtm/api/managing-access-tokens).\nIf you include an access token in the header of a request to the API  for data, it must have the scopes required by that endpoint. Access tokens are shown in the examples as: `Authorization: Bearer {access-token}`\n",
+        "required": false,
+        "routing": {
+            "request": {
+                "headers": {
+                    "Authorization": "={{ 'Bearer ' + $value }}"
+                }
+            }
+        },
+        "displayOptions": {
+            "show": {
+                "resource": [
+                    "Projects"
+                ],
+                "operation": [
+                    "Delete Project"
+                ]
+            }
+        }
+    },
+    {
+        "displayName": "GET /projects/{project-id}",
+        "name": "operation",
+        "type": "notice",
+        "typeOptions": {
+            "theme": "info"
+        },
+        "default": "",
+        "displayOptions": {
+            "show": {
+                "resource": [
+                    "Projects"
+                ],
+                "operation": [
+                    "Get Project"
+                ]
+            }
+        }
+    },
+    {
+        "displayName": "Project ID",
+        "name": "project-id",
+        "required": true,
+        "description": "The numeric project identifier",
+        "default": 0,
+        "type": "number",
+        "displayOptions": {
+            "show": {
+                "resource": [
+                    "Projects"
+                ],
+                "operation": [
+                    "Get Project"
+                ]
+            }
+        }
+    },
+    {
+        "displayName": "Bearer Token",
+        "name": "security_access_token",
+        "type": "string",
+        "default": "",
+        "description": "\n\nLGTM Enterprise users need to create and use an access token to authenticate with this API. This is optional for LGTM.com users unless they want to submit a CodeQL query for analysis of one or more projects, or to request the analysis of a patch or commit. LGTM.com users also need an access token to  check on the progress of long running tasks using the `/operations` endpoint.\nLog in to LGTM and use the **Create token** option in your Account settings page. For more detailed information, see [Authentication with the API](https://lgtm.com/help/lgtm/api/authentication-api) and [Managing access tokens](https://lgtm.com/help/lgtm/api/managing-access-tokens).\nIf you include an access token in the header of a request to the API  for data, it must have the scopes required by that endpoint. Access tokens are shown in the examples as: `Authorization: Bearer {access-token}`\n",
+        "required": false,
+        "routing": {
+            "request": {
+                "headers": {
+                    "Authorization": "={{ 'Bearer ' + $value }}"
+                }
+            }
+        },
+        "displayOptions": {
+            "show": {
+                "resource": [
+                    "Projects"
+                ],
+                "operation": [
+                    "Get Project"
+                ]
+            }
+        }
+    },
+    {
+        "displayName": "GET /projects/{project-id}/settings/analysis-configuration",
+        "name": "operation",
+        "type": "notice",
+        "typeOptions": {
+            "theme": "info"
+        },
+        "default": "",
+        "displayOptions": {
+            "show": {
+                "resource": [
+                    "Projects"
+                ],
+                "operation": [
+                    "Get Project Config"
+                ]
+            }
+        }
+    },
+    {
+        "displayName": "Project ID",
+        "name": "project-id",
+        "required": true,
+        "description": "The numeric project identifier",
+        "default": 0,
+        "type": "number",
+        "displayOptions": {
+            "show": {
+                "resource": [
+                    "Projects"
+                ],
+                "operation": [
+                    "Get Project Config"
+                ]
+            }
+        }
+    },
+    {
+        "displayName": "Source",
+        "name": "source",
+        "description": "The type of project configuration to retrieve.\nIf this parameter isn't specified, the request retrieves the effective configuration. That is, the configuration that is actually applied to the project, which may be from:\n* the repository\n* the administrator-set, project configuration\n* the global configuration.\n\nIf you do specify this value, it must be one of:\n\n * `repository` to retrieve the configuration specified by a YAML file in the repository. A 404 status is returned if there is no repository configuration. \n\n * `administrator` to retrieve the administrator-set, project configuration. A 404 status is returned if there is no administrator configuration.\n",
+        "default": "repository",
+        "type": "options",
+        "options": [
+            {
+                "name": "Repository",
+                "value": "repository"
+            },
+            {
+                "name": "Administrator",
+                "value": "administrator"
+            }
+        ],
+        "routing": {
+            "send": {
+                "type": "query",
+                "property": "source",
+                "value": "={{ $value }}",
+                "propertyInDotNotation": false
+            }
+        },
+        "displayOptions": {
+            "show": {
+                "resource": [
+                    "Projects"
+                ],
+                "operation": [
+                    "Get Project Config"
+                ]
+            }
+        }
+    },
+    {
+        "displayName": "Bearer Token",
+        "name": "security_access_token",
+        "type": "string",
+        "default": "",
+        "description": "\n\nLGTM Enterprise users need to create and use an access token to authenticate with this API. This is optional for LGTM.com users unless they want to submit a CodeQL query for analysis of one or more projects, or to request the analysis of a patch or commit. LGTM.com users also need an access token to  check on the progress of long running tasks using the `/operations` endpoint.\nLog in to LGTM and use the **Create token** option in your Account settings page. For more detailed information, see [Authentication with the API](https://lgtm.com/help/lgtm/api/authentication-api) and [Managing access tokens](https://lgtm.com/help/lgtm/api/managing-access-tokens).\nIf you include an access token in the header of a request to the API  for data, it must have the scopes required by that endpoint. Access tokens are shown in the examples as: `Authorization: Bearer {access-token}`\n",
+        "required": false,
+        "routing": {
+            "request": {
+                "headers": {
+                    "Authorization": "={{ 'Bearer ' + $value }}"
+                }
+            }
+        },
+        "displayOptions": {
+            "show": {
+                "resource": [
+                    "Projects"
+                ],
+                "operation": [
+                    "Get Project Config"
+                ]
+            }
+        }
+    },
+    {
+        "displayName": "PUT /projects/{project-id}/settings/analysis-configuration",
+        "name": "operation",
+        "type": "notice",
+        "typeOptions": {
+            "theme": "info"
+        },
+        "default": "",
+        "displayOptions": {
+            "show": {
+                "resource": [
+                    "Projects"
+                ],
+                "operation": [
+                    "Set Project Config"
+                ]
+            }
+        }
+    },
+    {
+        "displayName": "Project ID",
+        "name": "project-id",
+        "required": true,
+        "description": "The numeric project identifier",
+        "default": 0,
+        "type": "number",
+        "displayOptions": {
+            "show": {
+                "resource": [
+                    "Projects"
+                ],
+                "operation": [
+                    "Set Project Config"
+                ]
+            }
+        }
+    },
+    {
+        "displayName": "PUT /projects/{project-id}/settings/analysis-configuration<br/><br/>There's no body available for request, kindly use HTTP Request node to send body",
+        "name": "operation",
+        "type": "notice",
+        "default": "",
+        "displayOptions": {
+            "show": {
+                "resource": [
+                    "Projects"
+                ],
+                "operation": [
+                    "Set Project Config"
+                ]
+            }
+        }
+    },
+    {
+        "displayName": "Bearer Token",
+        "name": "security_access_token",
+        "type": "string",
+        "default": "",
+        "description": "\n\nLGTM Enterprise users need to create and use an access token to authenticate with this API. This is optional for LGTM.com users unless they want to submit a CodeQL query for analysis of one or more projects, or to request the analysis of a patch or commit. LGTM.com users also need an access token to  check on the progress of long running tasks using the `/operations` endpoint.\nLog in to LGTM and use the **Create token** option in your Account settings page. For more detailed information, see [Authentication with the API](https://lgtm.com/help/lgtm/api/authentication-api) and [Managing access tokens](https://lgtm.com/help/lgtm/api/managing-access-tokens).\nIf you include an access token in the header of a request to the API  for data, it must have the scopes required by that endpoint. Access tokens are shown in the examples as: `Authorization: Bearer {access-token}`\n",
+        "required": false,
+        "routing": {
+            "request": {
+                "headers": {
+                    "Authorization": "={{ 'Bearer ' + $value }}"
+                }
+            }
+        },
+        "displayOptions": {
+            "show": {
+                "resource": [
+                    "Projects"
+                ],
+                "operation": [
+                    "Set Project Config"
+                ]
+            }
+        }
+    },
+    {
+        "displayName": "GET /projects/{provider}/{org}/{name}",
+        "name": "operation",
+        "type": "notice",
+        "typeOptions": {
+            "theme": "info"
+        },
+        "default": "",
+        "displayOptions": {
+            "show": {
+                "resource": [
+                    "Projects"
+                ],
+                "operation": [
+                    "Get Project By URL Identifier"
+                ]
+            }
+        }
+    },
+    {
+        "displayName": "Provider",
+        "name": "provider",
+        "required": true,
+        "description": "The first part of the URL identifier of a project, which represents the repository host.",
+        "default": "",
+        "type": "string",
+        "displayOptions": {
+            "show": {
+                "resource": [
+                    "Projects"
+                ],
+                "operation": [
+                    "Get Project By URL Identifier"
+                ]
+            }
+        }
+    },
+    {
+        "displayName": "Org",
+        "name": "org",
+        "required": true,
+        "description": "The second part of the URL identifier of a project, the organization.",
+        "default": "",
+        "type": "string",
+        "displayOptions": {
+            "show": {
+                "resource": [
+                    "Projects"
+                ],
+                "operation": [
+                    "Get Project By URL Identifier"
+                ]
+            }
+        }
+    },
+    {
+        "displayName": "Name",
+        "name": "name",
+        "required": true,
+        "description": "The third part of the URL identifier of a project, the repository name.",
+        "default": "",
+        "type": "string",
+        "displayOptions": {
+            "show": {
+                "resource": [
+                    "Projects"
+                ],
+                "operation": [
+                    "Get Project By URL Identifier"
+                ]
+            }
+        }
+    },
+    {
+        "displayName": "Bearer Token",
+        "name": "security_access_token",
+        "type": "string",
+        "default": "",
+        "description": "\n\nLGTM Enterprise users need to create and use an access token to authenticate with this API. This is optional for LGTM.com users unless they want to submit a CodeQL query for analysis of one or more projects, or to request the analysis of a patch or commit. LGTM.com users also need an access token to  check on the progress of long running tasks using the `/operations` endpoint.\nLog in to LGTM and use the **Create token** option in your Account settings page. For more detailed information, see [Authentication with the API](https://lgtm.com/help/lgtm/api/authentication-api) and [Managing access tokens](https://lgtm.com/help/lgtm/api/managing-access-tokens).\nIf you include an access token in the header of a request to the API  for data, it must have the scopes required by that endpoint. Access tokens are shown in the examples as: `Authorization: Bearer {access-token}`\n",
+        "required": false,
+        "routing": {
+            "request": {
+                "headers": {
+                    "Authorization": "={{ 'Bearer ' + $value }}"
+                }
+            }
+        },
+        "displayOptions": {
+            "show": {
+                "resource": [
+                    "Projects"
+                ],
+                "operation": [
+                    "Get Project By URL Identifier"
+                ]
+            }
+        }
+    },
+];
+//# sourceMappingURL=index.js.map