Sandbox Management

As a Caliper SDK member, you can access a sandbox development environment shared with others in your group. For instance, if you are in the ‘sdkdemo’ group, there could be many others using the same ‘retail0’ user. We provide sample data for this user, but you might need additional users or data. With others using the same user, there is a possibility of locking out the user or needing to change the password. We have command line tools to help you manage these tasks.

Note

When using any q2 commands, please remember the -h option will display useful arguments or options. Most entrypoints provide a step-by-step prompt to walk you through its functionality. All entrypoints are for development use only.

User And Account Management

Unlock User

Locked out? To unlock user ‘retail0’ run q2 db unlock_user retail0.

Reset Password

To reset the password for retail0, you can use q2 db reset_password retail0. For the default user retail0, you can also reset the password from your dashboard.

Create a New Online User

To create a new user, just run q2 create_online_user.

Select the group, first name, last name, login name, primary CIF and tax ID for your user. Once the user is created, you will be provided with a temporary password.

Add New Account

To add a new account for testing, add HADE information, or link a new account to a specific user login, run q2 add_new_account. Linked accounts will appear on next login.

Environment Names

A note on lingo: when we discuss environments, your development sandbox is considered your “dev” environment. Q2 uses varying names for a permanent test environment (PTE), but we generally refer to these as “Staging”. Production is simply and always “Production”.

Core Connectivity

There is no core connectivity in your development sandbox, so you will be using mock responses, part of the Query component class for coreflow development. Once in Staging you can test code against your test core before going to Production.