[spaceship] spaceauth - add new functionality to check if a user's session is still valid #19658
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Checklist
bundle exec rspec
from the root directory to see all new and existing tests passbundle exec rubocop -a
to ensure the code style is validMotivation and Context
For CI testing it would be useful to quickly/succinctly tell if a
spaceship
session for a specific user is still valid. This would allow a CI build to immediately fail a task that requires authentication if the session is expired/missing.Description
This PR adds a new parameter,
--check_session
, to expose existing code in thespaceauth
command. Using the new parameter allows users to check if a session is still valid. If the session is valid the command will exit with a status code of 0, if the session is invalid it will exit with a status code of 1.Example Usage:
Testing Steps
Testing via the CLI should be pretty straightforward, recommend testing with and without a user set in the
Appfile
and testing with real and fake usernames.There are also 3 new tests that can be run locally: