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.

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

Exit with error if no launchpad found #253

Merged
merged 1 commit into from
Apr 19, 2022
Merged

Exit with error if no launchpad found #253

merged 1 commit into from
Apr 19, 2022

Conversation

brk3
Copy link
Contributor

@brk3 brk3 commented Apr 12, 2022

In the case where no matching environment is found or the user doesn't
have enough permissions, we should exit with non zero. An example use
case is where I mistype or otherwise forget to set my environment, rover
will output the "There is no remote state for ..." message, but in a
pipeline can look like it has passed.

In the case where no matching environment is found or the user doesn't
have enough permissions, we should exit with non zero. An example use
case is where I mistype or otherwise forget to set my environment, rover
will output the "There is no remote state for ..." message, but in a
pipeline can look like it has passed.
@arnaudlh arnaudlh requested a review from LaurentLesle April 14, 2022 08:52
@arnaudlh arnaudlh added the bug Something isn't working label Apr 14, 2022
Copy link
Member

@arnaudlh arnaudlh left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@arnaudlh arnaudlh merged commit 0033bed into aztfmod:main Apr 19, 2022
@arnaudlh
Copy link
Member

thanks for your contribution @brk3!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants