Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Spike: Can we retire global-digital-land-infrastructure? #293

Open
cpcundill opened this issue Feb 25, 2025 · 0 comments
Open

Spike: Can we retire global-digital-land-infrastructure? #293

cpcundill opened this issue Feb 25, 2025 · 0 comments

Comments

@cpcundill
Copy link
Contributor

cpcundill commented Feb 25, 2025 •
edited
Loading

Overview
Investigate what AWS resources, if any, are managed by the global-digital-land-infrastructure repository. Catalogue any such resources so we can determine next steps toward retiring this repository and collapsing any responsibility into the digital-land-infrastructure repository.

Tech Approach

  • Investigate the state associated with the repository in each environment
  • Catalogue the work to retire/refactor in new GitHub tickets
  • Email GDS to confirm understanding of how NS records are setup for planning.data.gov.uk

Acceptance Criteria/Tests

  • Clear set of work tickets which detail the work required to retire the repository
@cpcundill cpcundill moved this to Refine, Prioritise & Plan in Infrastructure Feb 25, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
Infrastructure
Status: Refine, Prioritise & Plan
Milestone
No milestone
Development

No branches or pull requests
1 participant
@cpcundill