-
Notifications
You must be signed in to change notification settings - Fork 34
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
Feature: Automate getting started guide #1228
Comments
This does not make much sense, would we spin up multiple images each for a unique provider ? Why not just make it work directly with the cloud CLIs (if possible) without images. With this the CLI/scripts could be run directly on the HOST or in a single docker container (possibly if the CLI/scripts would also install the necessary dependent cloud CLI's if not present on the HOST) |
I agree with the statement @Despire . I suggest to pack the resulting CLI in a docker image with provider CLIs. |
Motivation
When preparing for a new Claudie demo on new project, creating the accounts is susceptible to copy/paste mistakes and takes a substantial amount of time. Even when not using DNS and LBs, I need to account for ~2 hrs of time per one cloud provider and the result is not guaranteed. The approach of copy/pasting 10-11 commands per cloud provider has the following risks:
fish
orzsh
)userocid
anduser_ocid
) - difficult to check the syntax of the commandsoci
aws
orgcloud
especially if a user already has them bound to different accounts/projectsDescription
I'd expect to have an interactive command-line CLI/script, that would:
Exit criteria
The text was updated successfully, but these errors were encountered: