Skip to main content

Staging Instances

API Calls​

API calls are made in a similar way to the review instances above. Note that your API client may not connect to staging if going through the SOCKS proxy. The API URL for staging is: staging-api.va.gov/mobile. Staging uses the same API tokens as review instances.

curl --request GET \
  --url https://staging-api.va.gov/mobile/v1/user \
  --header 'Authorization: Bearer 6qdITmRgDqEmsdGyzNj7' \
  --header 'X-Key-Inflection: camel'

Console Access​

To connect to a staging instance, first ensure you have requested access to EKS.

After you have access, you can see the staging pods through the web. After signing in with your account and visiting the link, you will see several things

At the top, you'll see the last time the pods were synced to HEAD. On the right, you'll see a long list of pods running the staging site. Click on one that has vets-api-web in the name.

You'll see "TERMINAL" as a tab. From here, you have access to the console. You can run any commands you would in a local terminal here. For instance, run bundle exec rails c if you'd like to run a rails console.

User Sign In​

You can then fetch an api token and use that token to create a SIS user session:

irb(main):001:0> token = SignIn::AccessTokenJwtDecoder.new(access_token_jwt: 'crazylongsistoken').perform(with_validation: true)
irb(main):001:0> user = User.find(token.user_uuid)

If the user comes back as nil, this means it's not in redis due to inactivity. If that happens, make any API request for the user and try again. The API request will load the user into redis as part of the authentication process.