Support to install atest in Docker and Kubernetes

[LinuxSuRen]

atest could install as a Linux or macOS service according to the OS until v0.0.12. See also the following output. See the code lines of this sub-command

# atest service
Error: not support action: ''
Usage:
  atest service [flags]

Aliases:
  service, s

Flags:
  -a, --action string        The action of service, support actions: install, start, stop, restart, status
  -h, --help                 help for service
      --script-path string   The service script file path

atest could run in Docker or Kubernetes as well. So, it's good to support installing in Docker and Kubernetes. You could find the Kubernetes manifest files.

In order to specify the target environment, we could add a new flag --target. For example:

atest service install --target (os | docker | kubernetes)

Considering the compatibility, we could make the default value of --target to be os.

[colommar]

Hi, I'm a learner of go language and full stack and I'm interested in this repo, so I'd like to start with this GOOD FIRST ISSUE, what I can understand is: you need me to add download options for linux and docker. But how do I add them? I was starting to think it should be added in a file like make.sh, but I realized I didn't find anything like that.

[LinuxSuRen]

First, I need to say sorry about this issue. Consider this feature can be independent. I already moved it to a new repository go-service. Please go ahead if this situation does not bother you.

As you can see from the following document. There are multiple ways to install atest. For example:

• Linux, Windows, macOS service
• Run as a single container or docker-compose
• Run in Kubernetes as helm chart or other ways

https://linuxsuren.github.io/api-testing/#installation

So I'm thinking about how to make it easier. For instance, we can install it like: atest service --target kubernetes --source oci://docker.io/surenpi/api-testing --source-opt key=value. Hopefully, it's clear enough for you.

Finally, I guess this issue relates to two repositories.

[colommar]

Since it was moved to a new repo, I guess this issue can be closed, right? : )

[LinuxSuRen]

IMO, go-service will complete the most work, and this project still need to call the relevant functions to finish this issue.