Eugen

Looking closer, there are plugin env validation scripts already: * Helm: https://github.com/bitops-plugins/helm/blob/main/scripts/validate_env.sh * Ansible: https://github.com/bitops-plugins/ansible/blob/main/scripts/validate_env.sh * Terraform: https://github.com/bitops-plugins/terraform/blob/main/scripts/validate_env.sh There is no one for AWS though: https://github.com/bitops-plugins/aws so @ccapell you can...

Following the issue [Custom image build reports success on a failed plugin installation #239](https://github.com/bitovi/bitops/issues/239), the plugins should have tests and CI/CD, ensuring that they could be built properly. In the...

@ConnorGraham suggested `bitops init` for this kind of CLI entry point.

Cool stuff with experimentation 👍 With the `Golang` approach, it's easy to ship the binary separately (no need to have yo/npm like in the past or python). If we do...

Speaking of Golang in general, I believe it's initially the best approach for BitOps and CLI, considering the Golang popularity in DevOps and the cloud-native world. But because we're on...

The dir sync just works out of the box. When the user executes `docker run -v $(pwd):/opt/bitops_deployment ` it's a bi-directional dir sharing. Writes made from bitops will show up...

Private Github repository could be already cloned via `https://username:[email protected]/username/repo_name.git` For git cloning with SSH key, the user can mount his SSH key to the BitOps container and specify it in...

Going with a simple documentation case first might be a good intermediate state. If we want to go deeper, from the proposals above, providing `ENV` or `path` for the SSH...

In a minimum implementation `complexity: easy` effort, just add a small paragraph to the docs, providing an existing way to install a private plugin from the Github repo with github...

Do we Error it out with some validation message on the code side in the case when the reserved word is used in a wrong way? Feels like a validation...