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

different "environments" for the juno.json #40

Closed
peterpeterparker opened this issue Aug 23, 2023 · 2 comments · Fixed by #91 or #95
Closed

different "environments" for the juno.json #40

peterpeterparker opened this issue Aug 23, 2023 · 2 comments · Fixed by #91 or #95
Assignees
@peterpeterparker

Comments

@peterpeterparker
Copy link
Contributor

is it also possible to specify different "environments" in the juno.json file that we can tag on certain deployment varaibles?
@peterpeterparker peterpeterparker added the good first issue Good for newcomers label Aug 23, 2023
@peterpeterparker
Copy link
Contributor Author

peterpeterparker commented Jan 21, 2024 •
edited
Loading

In addtion maybe we should refactor/rename the cli profile/use command to env.

Not a good idea. If we do that we will have env for the controllers and env for the config.

@peterpeterparker peterpeterparker removed the good first issue Good for newcomers label Feb 16, 2024
@peterpeterparker peterpeterparker self-assigned this Feb 16, 2024
This was linked to pull requests Feb 16, 2024
feat: support multiple environments with --mode #91
Merged
feat: add support for satelliteIds to config #95
Merged
@peterpeterparker
Copy link
Contributor Author

This has been resolved. Configuration files support multiple env.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@peterpeterparker peterpeterparker

Labels
None yet
Projects
None yet
Milestone
No milestone
1 participant
@peterpeterparker