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.

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

epic: Deploy project to AWS (dev) #297

Open
3 tasks
Tracked by #218
fyliu opened this issue Jun 6, 2024 · 2 comments
Open
3 tasks
Tracked by #218

epic: Deploy project to AWS (dev) #297

fyliu opened this issue Jun 6, 2024 · 2 comments
Labels
complexity: small All steps are laid out in detail so that someone new to the project can work on it epic Issue is an epic feature: infrastructure For changes on site technical architecture ready for product role: dev ops s: PD team stakeholder: People Depot Team size: 8pt Can be done in 31-48 hours

Comments

@fyliu
Copy link
Member

fyliu commented Jun 6, 2024

Dependency

Overview

Once we're ready, we need to set up the resources with someone in #OPS to deploy the project so that a client can connect to an always-running instance. This includes Terraform resources, etc.

Action Items

@fyliu fyliu added size: 8pt Can be done in 31-48 hours feature: infrastructure For changes on site technical architecture s: PD team stakeholder: People Depot Team role: dev ops ready for product labels Jun 6, 2024
@fyliu fyliu added this to the v0.01 - initial setup milestone Jun 6, 2024
@fyliu fyliu changed the title Deploy project in OPS Deploy project to AWS Jun 6, 2024
@ExperimentsInHonesty
Copy link
Member

ExperimentsInHonesty commented Jun 24, 2024

@fyliu I think this issue is too big. Please break it down into separate issues and maybe treat this issue as an epic. At a minimum

Issue 1

Notes:

  1. If the deployment checklist they have (if they have one at all) is not complete or inaccurate, we need to help them make a comprehensive one and update it in their wiki, so that it gets sign-off by them and we can use it.
  2. if ops creates an issue, link to it here

Issue 2 (epic)

Notes: each of these issues should involve asking ops to verify setup (through the PR process)

Issue 2.1

Issue 2.2

Issue 2.3

Issue 3

Notes: I am not 100% sure what you are saying here... we can talk more about it on the draft of the issue.

fang: updated to add issue numbers to items

@fyliu fyliu added the epic Issue is an epic label Jun 27, 2024
@fyliu fyliu added complexity: small All steps are laid out in detail so that someone new to the project can work on it ready for product and removed complexity: missing ready for dev lead labels Aug 9, 2024
@fyliu fyliu changed the title Deploy project to AWS epic: Deploy project to AWS Aug 19, 2024
@fyliu fyliu changed the title epic: Deploy project to AWS epic: Deploy project to AWS (dev) Aug 19, 2024
@fyliu
Copy link
Member Author

fyliu commented Aug 19, 2024

I created the smaller issues. This is pending PM review of this and the smaller issues. Otherwise it's ready for prioritization.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
complexity: small All steps are laid out in detail so that someone new to the project can work on it epic Issue is an epic feature: infrastructure For changes on site technical architecture ready for product role: dev ops s: PD team stakeholder: People Depot Team size: 8pt Can be done in 31-48 hours
Projects
Status: 🆕New Issue Review
Development

No branches or pull requests

2 participants