DRAFT - 3618: script to update public contact org city state

[chaswick]

Ticket

Resolves #3618

Changes

• New Django management command to call the website method that will update public contacts using the latest code which supports partial disclosure of the address
• Leverages the code changes made in Connect "public contact" values for Registrant to actual registrant values #3580 in def _disclose_fields(self, contact:PublicContact) to set the epp disclosure settings per our requirements.

Context for reviewers

Setup

TBD

Code Review Verification Steps

As the original developer, I have

Satisfied acceptance criteria and met development standards

• Met the acceptance criteria, or will meet them in a subsequent PR
• Created/modified automated tests
• Update documentation in READMEs and/or onboarding guide

Ensured code standards are met (Original Developer)

• If any updated dependencies on Pipfile, also update dependencies in requirements.txt.
• Interactions with external systems are wrapped in try/except
• Error handling exists for unusual or missing values

Validated user-facing changes (if applicable)

• Follow the process for requesting a design review. If code is not user-facing, delete design reviewer checklist
• Verify new pages have been added to .pa11yci file so that they will be tested with our automated accessibility testing
• Checked keyboard navigability
• screen reader (such as NVDA with Chrome or Voiceover with Safari):
  • Tested general usability
  • landmarks
  • page header structure
  • links
• Checked for errors or warnings with an a11y browser tool (such as ANDI or WAVE)

As a code reviewer, I have

Reviewed, tested, and left feedback about the changes

• Pulled this branch locally and tested it
• Verified code meets all checks above. Address any checks that are not satisfied
• Reviewed this code and left comments. Indicate if comments must be addressed before code is merged
• Checked that all code is adequately covered by tests
• Verify migrations are valid and do not conflict with existing migrations

Validated user-facing changes as a developer

Note: Multiple code reviewers can share the checklists above, a second reviewer should not make a duplicate checklist. All checks should be checked before approving, even those labeled N/A.

• New pages have been added to .pa11yci file so that they will be tested with our automated accessibility testing
• Checked keyboard navigability
• Meets all designs and user flows provided by design/product
• screen reader (such as NVDA with Chrome or Voiceover with Safari):
  • Tested general usability
  • landmarks
  • page header structure
  • links
• Checked for errors or warnings with an a11y browser tool (such as ANDI or WAVE)
• (Rarely needed) Tested as both an analyst and applicant user

As a designer reviewer, I have

Verified that the changes match the design intention

• Checked that the design translated visually
• Checked behavior. Comment any found issues or broken flows.
• Checked different states (empty, one, some, error)
• Checked for landmarks, page heading structure, and links

Validated user-facing changes as a designer

• Checked keyboard navigability
• screen reader (such as NVDA with Chrome or Voiceover with Safari):
  • Tested general usability
  • landmarks
  • page header structure
  • links
• Checked for errors or warnings with an a11y browser tool (such as ANDI or WAVE)
• Tested with multiple browsers (check off which ones were used)
  • Chrome
  • Microsoft Edge
  • FireFox
  • Safari
• (Rarely needed) Tested as both an analyst and applicant user

References

• Code review best practices

Screenshots

[github-actions]

🥳 Successfully deployed to developer sandbox cw.

[github-actions]

🥳 Successfully deployed to developer sandbox cw.

[github-actions]

🥳 Successfully deployed to developer sandbox cw.

[github-actions]

🥳 Successfully deployed to developer sandbox cw.