coollabsio / coollabsio/coolify-cli
make api client not internal
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 467
- Forks
- 69
- PR merge metrics
- No merged PRs in 30d
Description
Hi,
I am currently building https://github.com/bambamboole/pulumi-provider-coolify .
There I had to re-implement the API client, because here in this package it is in internal.
Do you think, coolify could release a go api-client, which is then used by the cli ?
Or would you accept a PR moving the client code out of internal ?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading the API client under internal and the CLI call sites that use it. Determine whether the client should become a public Go package or remain internal, and check the implications for external consumers such as the linked Pulumi provider. Done means the project has an agreed public-client direction and the CLI continues to use the supported client.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- api, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100