apiVersion: kabanero.io/v1alpha1 kind: Kabanero metadata: name: kabanero namespace: kabanero spec: collections: repositories: - name: custom url: https://github.example.com/my_org/collections/releases/download/0.3.0/kabanero-index.yaml activateDefaultCollections: true github: organization: my_org teams: - collection-admins - admins apiurl: api.github.com
You can modify your Kabanero CR instance to provide authorization to the teams in GitHub that will administer the collection(s). If you do not already have a team defined, see Creating teams in GitHub.
Spec.Github.organizationattribute should be set to the organization hosting the collections in the remote GitHub repository. In the example above, the organization name is
Spec.Github.teamsattribute should be set to a yaml list of GitHub teams in the remote GitHub repository, whose members can administer the collection using the Kabanero CLI.
Spec.Github.apiurlattribute should be set to the API URL for the remote GitHub repository being used. For example, the API URL for
A modified Kabanero CR instance for a collection repository located in the
my_orgorganization of the
github.example.comGitHub repository using release
0.3.0of collections might look like this: