Skip to content
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.

Sign up for GitHub

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

Jump to bottom

airshipctl base commands (example from Jira) #1

Closed
drewwalters96 opened this issue Jan 16, 2020 · 1 comment
Closed

airshipctl base commands (example from Jira) #1

drewwalters96 opened this issue Jan 16, 2020 · 1 comment
Assignees
@jezogwza

Comments

@drewwalters96
Copy link
Contributor

Both the CLI and the UI will need to be able to leverage a standard k8ssecurity context for interacting with remote sites. It should also understandAirship site contexts so that it can be pointed at a local document set andwork with that during subsequent commands without needingto be fed the same document set with every command similar to interactingwith the same Kubernetes cluster throughout a kubectl session.

The initial proposed list of commands that will be implemented is defined below:

Every command will support :

GENERIC OPTIONS

-----------------------------------------------------------------+

NAME

USAGE

=================================================================+

help

Help for the appropriate command

it also lists available plugins

-----------------------------------------------------------------+

version

Version of airshipctl.

-----------------------------------------------------------------+
@jezogwza
Copy link
Contributor

This was achieved already with merged patchset https://review.opendev.org/#/c/689859/

@airshipbot airshipbot mentioned this issue Oct 9, 2020
Closed
airshipbot pushed a commit that referenced this issue Nov 2, 2020
@teoyaomiqui
Phase documentation part #1
6059f42 
Add phase execution engine scaffolding to documentation.

Also add general architecture of phases, and brief description of
what phases, executors and bundles are.

Next commits will fill in the placeholders and topics in the
documentation, such as metadata and phase plan.

Relates-To: #360

Change-Id: Icac00b046cf50d18a71ca69ef9ecbb8be612f9ab
airshipbot pushed a commit that referenced this issue Nov 2, 2020
@openstack-gerrit
Merge "Phase documentation part #1"
2257655
@mattmceuen mattmceuen mentioned this issue Mar 9, 2021
Closed
@jgu17 jgu17 mentioned this issue Apr 30, 2021
Closed
@eak13 eak13 mentioned this issue Oct 20, 2021
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@jezogwza jezogwza

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jezogwza @drewwalters96