Skip to content
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.

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

[Improvement]: Add local repository support to the bal tool #41729

Closed
Thevakumar-Luheerathan opened this issue Nov 20, 2023 · 0 comments · Fixed by #41763
Closed

[Improvement]: Add local repository support to the bal tool #41729

Thevakumar-Luheerathan opened this issue Nov 20, 2023 · 0 comments · Fixed by #41763
Assignees
Labels
needTriage The issue has to be inspected and labeled manually Type/Improvement userCategory/Compilation

Comments

@Thevakumar-Luheerathan
Copy link
Member

Description

Publish a tool to the local repository
bal push --repository=local

  • Copies the bala to the local repo locations and extract.
  • Keeps a mapping between tool-Id and org-package name to retrieve them easily with pulling

Use a tool from the local repository

bal tool pull <tool-id>:<version> --repository local

  • Adds the tool entry to the bal-tools.toml
[[tool]]
id = openapi
org = ballerina
name = tool-openapi
version = 1.0.1
repository = local
active = true
  • This makes the tool available to the user locally and sets it as the active version.

Switch to another version of a tool in the local repository
bal tool use <tool-id>:<version> --repository local

Remove the usage of the tool from the local repository

  • Option 1: Execute the bal tool use command to switch to the required version

      `bal tool use <tool-id>:<version>`
    
  • Option 2: Remove command removes the entry from bal-tools.toml

      `bal tool remove <tool-id>:<version> --repository local`
    

Describe your problem(s)

No response

Describe your solution(s)

No response

Related area

-> Compilation

Related issue(s) (optional)

No response

Suggested label(s) (optional)

No response

Suggested assignee(s) (optional)

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needTriage The issue has to be inspected and labeled manually Type/Improvement userCategory/Compilation
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants