Cassandra/Staging
This page is currently a draft.
Material may not yet be complete, information may presently be omitted, and certain parts of the content may be subject to radical, rapid alteration. More information pertaining to this may be available on the talk page.
Material may not yet be complete, information may presently be omitted, and certain parts of the content may be subject to radical, rapid alteration. More information pertaining to this may be available on the talk page.
This cluster should not be used for general development work, but to stage changes destined for production; Do not deploy changes or carry out activities that you do not expect to likewise rollout to production.
To obtain developer access, follow the usual process for submitting an access request.
After obtaining access, you can run cqlsh by using sudo and the surrogate user cassandra_devel. This user has been pre-configured for access using a dedicated Cassandra role (also named cassandra_devel).
user@home: ~$ ssh cassandra-dev2001.codfw.wmnet
user@cassandra-dev2001:~$ sudo -u cassandra_devel cqlsh cassandra-dev2001-a
Connected to cassandra-dev at cassandra-dev2001-a:9042
[cqlsh 6.1.0 | Cassandra 4.1.1 | CQL spec 3.4.6 | Native protocol v5]
Use HELP for help.
cassandra_devel@cqlsh>
As cassandra_devel you can read, write, and delete to all tables (not just those owned by you or your team), so be a good neighbor.