Skip to content

fix: Use list(string) instead of tuple for some of the output variables #380

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Mar 10, 2025
Merged

fix: Use list(string) instead of tuple for some of the output variables #380

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
28 changes: 14 additions & 14 deletions metadata.yaml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -342,41 +342,41 @@ spec:
- name: external_table_ids
description: Unique IDs for any external tables being provisioned
type:
- tuple
- []
- list
- string
- name: external_table_names
description: Friendly names for any external tables being provisioned
type:
- tuple
- []
- list
- string
- name: project
description: Project where the dataset and tables are created
type: string
- name: routine_ids
description: Unique IDs for any routine being provisioned
type:
- tuple
- []
- list
- string
- name: table_ids
description: Unique id for the table being provisioned
type:
- tuple
- []
- list
- string
- name: table_names
description: Friendly name for the table being provisioned
type:
- tuple
- []
- list
- string
- name: view_ids
description: Unique id for the view being provisioned
type:
- tuple
- []
- list
- string
- name: view_names
description: friendlyname for the view being provisioned
type:
- tuple
- []
- list
- string
requirements:
roles:
- level: Project
Expand Down