zydronium/manage.get.gov
1
0
Fork 0
mirror of https://github.com/cisagov/manage.get.gov.git synced 2025-07-22 02:36:02 +02:00
Code Issues Projects Releases Packages Wiki Activity

update import_tables documentation

Browse source
This commit is contained in:
David Kennedy 2024-06-11 07:09:11 -04:00
parent 77e5c918e7
commit b3a272025d
No known key found for this signature in database
GPG key ID: 6528A5386E66B96B
1 changed files with 10 additions and 1 deletions
Download patch file Download diff file Expand all files Collapse all files

11
docs/operations/import_export.md
View file

@ -35,6 +35,7 @@ For reference, the zip file will contain the following tables in csv form:
* Websites
* Host
* HostIP
* PublicContact
After exporting the file from the target environment, scp the exported_tables.zip
file from the target environment to local. Run the below commands from local.
@ -81,11 +82,18 @@ For reference, this deletes all rows from the following tables:
* DraftDomain
* HostIP
* Host
* PublicContact
#### Importing into Target Environment
Once target environment is prepared, files can be imported.
If importing tables from stable environment into an OT&E sandbox, there will be a difference
between the stable's registry and the sandbox's registry. Therefore, you need to run import_tables
with --skipEppSave option set to False. If you set to False, it will attempt to save PublicContact
records to the registry on load. If this is unset, or set to True, it will load the database and not
attempt to update the registry on load.
To scp the exported_tables.zip file from local to the sandbox, run the following:
Get passcode by running:
@ -107,7 +115,7 @@ cf ssh {target-app}
example cleaning getgov-backup:
cf ssh getgov-backup
/tmp/lifecycle/backup
./manage.py import_tables
./manage.py import_tables --skipEppSave=False
For reference, this imports tables in the following order:
@ -121,6 +129,7 @@ For reference, this imports tables in the following order:
* DomainRequest
* DomainInformation
* UserDomainRole
* PublicContact
Optional step:
* Run fixtures to load fixture users back in