davidcardoso / my-ez-cli Goto Github PK

Blocked by #30 (#31).

Make CLI tooling-dev/cli ready to be public.

Describe the bug

I tried to capture the output in a variable.
But the gcloud command is returning the input device is not a TTY instead of the value of the output.

To Reproduce
Steps to reproduce the behavior:

1. Try something like this: var=$(gcloud storage ls)
2. You should get the error msg.

Expected behavior

Be able to capture output in a variable.

Screenshots
...

Desktop (please complete the following information):

• OS: MacOS
• Version 13.6

Additional context
...

Describe the bug
A warning msg regarding the mix of architecture/platform in MacOS using the recent Apple silicons is being showed every time a container is run.

To Reproduce
Steps to reproduce the behavior:

1. run ./bin/speedtest or ./bin/gcloud.
2. the warning msg should be displayed in the beginning of the output.

Expected behavior
Execute the commands via docker with no mix architecture being showed every time.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: MasOS Ventura
• Version 13.5.2 (22G91)

Additional context
...

Is your feature request related to a problem? Please describe.

We've faced some problems with GitLab NPM package registry using Yarn classic.

Although we could solve the problem by using Yarn Berry, it's good to keep both versions in a transition situation along with the dev team, for example.

Describe the solution you'd like

• Add Yarn Berry installation support.
• Give the option to replace the old Yarn OR keep both.

In the second case, the local machine will have available yarn and another called yarn-berry execs.

Describe alternatives you've considered

Use yarn berry binary inside the repo/project. But it implies committing the yarn binary in each project/repo.

So, instead, we can do this only here and use Yarn Berry over Docker.

Additional context

• Migrating an existent repo/project from npm/yarn classic

https://playwright.dev/docs/docker

• upgrade serverless framework version to v3.38.0
• upgrade node engine used by serverless framework to v20 LTS

Is your feature request related to a problem? Please describe.

...

Describe the solution you'd like

• Add Code Climate CLI via Docker.

Describe alternatives you've considered

It can be integrated to GitHub repos but would be handful be able to run Code Climate in local environment as well.

Additional context

https://hub.docker.com/r/codeclimate/codeclimate

Is your feature request related to a problem? Please describe.

Would be great to run dynamoDB locally to test local applications (e.g., Lambda Function).

Describe the solution you'd like

• add AWS DynamoDB local via Docker

Describe alternatives you've considered

It is possible to setup it via docker-compose or using Serverless Framework plugin.

Additional context

https://hub.docker.com/r/amazon/dynamodb-local/

Problem

Wrong text in EXIT option in help menu.

Line: https://github.com/Tooling-Dev/cli/blob/main/setup.sh#L31

Steps to reproduce

1 .Run the ./setup.sh script
2. choose a incorrect option
3. check the description of the EXIT option

Solution / Proposal

Correct the text for something like EXIT: To leave this menu.

• upgrade terraform version to 1.8.3
• update terraform section on README
• improve how aws, gcp, and TF cloud credentials are passed to the container
• add support to dotenv file
• improve how to pass a parent folder as CONTEXT to the container

Is your feature request related to a problem? Please describe.

• Misinformation about AWS SSO region.
• Project name has changed.

Describe the solution you'd like

• Delete note about AWS sso_region = us-east-1.
• Rename project name to match repo name in default files like LICENSE, README, CONTRIBUTION.

See line.

Describe alternatives you've considered

NA

Additional context

NA

Describe the bug

Not running.

Console logs:

docker: Error response from daemon: failed to create shim: OCI runtime create failed: container_linux.go:380: starting container process caused: exec: "/bin/bash": stat /bin/bash: no such file or directory: unknown.

To Reproduce

Try to run speedtest but it doesn't work properly.

Expected behavior

Running the speedtest cli corretly.

Screenshots
If applicable, add screenshots to help explain your problem.

Desktop (please complete the following information):

• OS: Ubuntu
• Version 20

Additional context

NA

Describe the bug

The installation of the npm dependency snappy required by @prisma/engines package failed because of the absence of Python in the docker image used by bin/yarn script.

See logs below.

To Reproduce

Steps to reproduce the behavior:

1. Go to the root folder of a NodeJS project where the package.json file is set up
2. Add Prisma as a dev dependency: yarn add [email protected] --dev
3. Run 'yarn' to install the dependencies

Expected behavior

Conclude the npm dependency installation without errors using the yarn command (bin/yarn).

Screenshots/Logs

warning Error running install script for optional dependency: "/app/node_modules/snappy: Command failed.
Exit code: 1
Command: prebuild-install || node-gyp rebuild
Arguments:
Directory: /app/node_modules/snappy
Output:
prebuild-install WARN install No prebuilt binaries found (target=16.20.0 runtime=node arch=x64 libc=musl platform=linux)
gyp info it worked if it ends with ok
gyp info using [email protected]
gyp info using [email protected] | linux | x64
gyp ERR! find Python
gyp ERR! find Python Python is not set from command line or npm configuration
gyp ERR! find Python Python is not set from environment variable PYTHON
gyp ERR! find Python checking if \"python3\" can be used
gyp ERR! find Python - \"python3\" is not in PATH or produced an error
gyp ERR! find Python checking if \"python\" can be used
gyp ERR! find Python - \"python\" is not in PATH or produced an error
gyp ERR! find Python
gyp ERR! find Python **********************************************************
gyp ERR! find Python You need to install the latest version of Python.
gyp ERR! find Python Node-gyp should be able to find and use Python. If not,
gyp ERR! find Python you can try one of the following options:
gyp ERR! find Python - Use the switch --python=\"/path/to/pythonexecutable\"
gyp ERR! find Python   (accepted by both node-gyp and npm)
gyp ERR! find Python - Set the environment variable PYTHON
gyp ERR! find Python - Set the npm configuration variable python:
gyp ERR! find Python   npm config set python \"/path/to/pythonexecutable\"
gyp ERR! find Python For more information consult the documentation at:
gyp ERR! find Python https://github.com/nodejs/node-gyp#installation
gyp ERR! find Python **********************************************************
gyp ERR! find Python
gyp ERR! configure error
gyp ERR! stack Error: Could not find any Python installation to use
gyp ERR! stack     at PythonFinder.fail (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/find-python.js:330:47)
gyp ERR! stack     at PythonFinder.runChecks (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/find-python.js:159:21)
gyp ERR! stack     at PythonFinder.<anonymous> (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/find-python.js:202:16)
gyp ERR! stack     at PythonFinder.execFileCallback (/usr/local/lib/node_modules/npm/node_modules/node-gyp/lib/find-python.js:294:16)
gyp ERR! stack     at exithandler (node:child_process:410:5)
gyp ERR! stack     at ChildProcess.errorhandler (node:child_process:422:5)
gyp ERR! stack     at ChildProcess.emit (node:events:513:28)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12)
gyp ERR! stack     at onErrorNT (node:internal/child_process:485:16)
gyp ERR! stack     at processTicksAndRejections (node:internal/process/task_queues:83:21)
gyp ERR! System Linux 5.15.90.1-microsoft-standard-WSL2
gyp ERR! command \"/usr/local/bin/node\" \"/usr/local/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js\" \"rebuild\"
gyp ERR! cwd /app/node_modules/snappy

Desktop (please complete the following information):

• OS: WSL Ubuntu
• Version 22.04.23 LTS

Additional context

Ensure you are using the bin/yarn script provided by this repository not a yarn binary directly installed on your OS.

Describe the solution you'd like
Be agnosticly (Mac, Linux, WSL) able to run gcloud cli commands via docker.

Describe alternatives you've considered
I can install cloud cli directly on each of my machines.

Is your feature request related to a problem? Please describe.

Simplify internet connection tests via Unix Terminal, and with no installation.

Describe the solution you'd like

Add speedtest CLI via Docker based on official documentation.

Run $ speedtest on terminal:

Describe alternatives you've considered

It is already available on web browser. However, it is not possible in OS's without UI (e.g., when only the terminal is available).

It is already available via linux packages but it requires installation.

Additional context

Using docker, we could run it in almost every distro compatible with docker containers.

Describe the solution you'd like

Generate dependency graph for docker-compose.[yaml|yml] files.

Additional context

https://github.com/pmsipilot/docker-compose-viz

• upgrade default node version to 20 LTS
• create aliases for node16 and node18
• upgrade default yarn alias to run on top of node 20 LTS
• create aliases for yarn16 and yarn18 to run on top of node16 and node18, respectively.
• add NPM_TOKEN env var to yarns scripts
• add binding ports to the container to yarns scripts
• update readme