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

Scan for environments in configured search paths #25

Open
MLNW opened this issue Mar 13, 2022 · 1 comment
Open

Scan for environments in configured search paths #25

MLNW opened this issue Mar 13, 2022 · 1 comment
Labels
enhancement New feature or request

Comments

@MLNW
Copy link
Contributor

MLNW commented Mar 13, 2022 •
edited
Loading

Currently, it is only possible to provide a file to the CLI instead of being provided with a list of available environments.

Related to #7
@MLNW MLNW added the enhancement New feature or request label Mar 13, 2022
@MLNW MLNW changed the title Scan for components in configured search paths Scan for environments in configured search paths Mar 13, 2022
MLNW added a commit that referenced this issue Apr 3, 2022
@MLNW
👔 Implement basic environment scanning
1e4d698 
An environment scanner now looks for environments and adds them via the
common registry pattern. Full integration with the CLI is missing as it
is currently unclear how to interact with environments.

The available deploy command already benefits from the changes by
utilizing the newly created SoftwareEnvironment class.

Related #25
@MLNW
Copy link
Contributor Author

MLNW commented Apr 3, 2022

The scanning is implemented but not yet fully integrated with the CLI. It must be decided upon how to integrate environments.

One possibility would be to add a dagos env list command to display them and allow providing them to dagos env deploy instead of a file. This option would be in contrast to how software components are currently handled.

Another option would be to list found environments when running dagos env deploy and allow deploying them with dagos env deploy <environment>.

A third option would be to have commands like dagos env <environment> info|deploy.

Generally, it must be decided on what kind of interactions should be possible for environments. Some possibilities below:

  • deploy
  • info?
  • update?
  • validate?
  • remove?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@MLNW