id values with the kosli_repo_tags resource to tag repos. To fetch a single repo, use the kosli_repo data source.
Data sources are read at plan time. A repo that Kosli first records later in the same pipeline is missing from
repos until the next plan. No match returns an empty list, not an error.Example usage
Schema
Optional
name(String) Return only repos with exactly this name, for exampleacme/platform/api. Conflicts withsearch.namespace(String) Return only repos nested anywhere under this/-separated namespace, for exampleacme/platform.search(String) Return only repos whose name contains this string (case-insensitive). Conflicts withname.tag_filter(Block List) Return only repos with a matching tag. Repos must match everytag_filterblock. See the nested schema below.vcs_instance(String) Return only repos on this VCS host, for examplegitlab.company.com.vcs_provider(String) Return only repos hosted by this VCS provider, for examplegithub,gitlab,bitbucketorazure-devops.
Read-only
repos(Attributes List) The matching repos, sorted by name and then byid. Empty when no repo matches. See the nested schema below.
Nested schema for tag_filter
Required:
key(String) Tag key the repo must have.
values(List of String) Values the tag may have; a repo matches if its tag has any of them. Omit to match the key with any value.
Nested schema for repos
Read-only:
id(String) Internal Kosli ID of the repo. Use it asrepo_idonkosli_repo_tags.name(String) Full name of the repo, including its namespace. Names can repeat across VCS providers.tags(Map of String) Key-value pairs tagging the repo.url(String) URL of the repo.vcs_instance(String) VCS host of the repo. Null when Kosli could not determine it.vcs_provider(String) VCS provider of the repo. Null when Kosli could not determine it.