Console Services: Provide Deployment Status of applications within Atlas

npeterson54 commented 2 years ago

This has been De-Prioritized due to the vets-api to Kubernetes move being a higher priority and team changes/contracts expiring.

Problem Statement

As a VSP developer within the platform console, there is no way for me to be able to see if a deployment of my application is up and running.

We might be able to address this by completing the integration with the Platform Infrastructure so that we are able to display an applications' deployment status.

Hypothesis or Bet

Once a deployment is made, a VSP developer will be able to see if their deployment was successful or not.
Having this information within the Platform Console will allow the users to stay within the Console and not search for this information elsewhere.

We will know we're done when... ("Definition of Done")

Users are able to see the following: Sync Status App Health Current Commit Previous Commit Deploy Times

Known Blockers/Dependencies

In order for us to display an apps deployment status, it first must be added to Argo.

Projected Launch Date

April 30, 2022

Launch Checklist

Is this service / tool / feature...

... tested?

[ ] Usability test (TODO: link) has been performed, to validate that new changes enable users to do what was intended and that these changes don't worsen quality elsewhere. If usability test isn't relevant for this change, document the reason for skipping it.
- [ ] ... and issues discovered in usability testing have been addressed.
- Note on skipping: metrics that show the impact of before/after can be a substitute for usability testing.
[ ] End-to-end manual QA or UAT is complete, to validate there are no high-severity issues before launching
[ ] (if applicable) New functionality has thorough, automated tests running in CI/CD

... documented?

[ ] New documentation is written pursuant to our documentation style guide
[ ] Product is included in the List of VSP Products
- List the existing product that this initiative fits within, or add a new product to this list.
[ ] Internal-facing: there's a Product Outline
[ ] External-facing: a User Guide on Platform Website exists for this product/feature tool
[ ] (if applicable) Post to #vsp-service-design for external communication about this change (e.g. customer-facing meetings)

... measurable

[ ] (if applicable) This change has clearly-defined success metrics, with instrumentation of those analytics where possible, or a reason documented for skipping it.
- For help, see: Analytics team
[ ] This change has an accompanying VSP Initiative Release Plan.

When you're ready to launch...

[ ] Conduct a [go/no-go] (https://vfs.atlassian.net/wiki/spaces/AP/pages/1670938648/Platform+Crew+Office+Hours#Go%2FNo-Go) when you're almost ready to launch.

Required Artifacts

Documentation

PRODUCT_NAME: directory name used for your product documentation
Product Outline: link to Product Outline
User Guide: link to User Guide

Testing

Usability test: link to GitHub issue, or provide reason for skipping
Manual QA: link to GitHub issue or documented results
Automated tests: link to tests, or "N/A"

Measurement

Success metrics: link to where success metrics are measured, or where they're defined (Product Outline is OK), or provide reason for skipping
Release plan: link to Release Plan ticket

TODOs

[x] Convert this issue to an epic
[x] Add your team's label to this epic

npeterson54 commented 2 years ago

We may have a dependency on the AMT team to get ARGO and Keycloak integrated - update: this is on their roadmap for Q2.

npeterson54 commented 2 years ago

Potential stories -[ ] Make API available -[ ] Documentation (started, not complete) -[ ] Investigate DEX locally

npeterson54 commented 2 years ago

This should be moved to the backlog/icebox. It has been de-prioritized.

EricaRobbins commented 1 year ago

@raywangoctova - I see this one has been closed in the repository. Can you please check the accuracy on this one? Is this work still pending? Thanks!

EricaRobbins commented 9 months ago

Console work has been on-hold for a long time. Moving this to the backlog, possibly needs a new title. Still a need. Follow up with Eric and update this card @BillChapmanUSDS

annekerr49 commented 7 months ago

Assign to Aparna and Jeff reopen Jonathan -This seems to be just like what version of each application is deployed to production. Bill - Eric picked that up a bit and it was in Atlas and then it was in something else for a bit. Whether this is in Atlas probably needs to be discussed with the Reliability team. Jeff - I should follow up - my understanding of this would be something that the developers want to utilize to understand the deployment status of their application Ray - I think you first need to understand what console service is versus console UI.

Console service is meant to do backend automations
Console UI is where the developer goes through an interface to interact and self service a lot of the work related to the deployment or to the application itself. My understanding is none of those works have been fully completed There are different teams for different pieces of that Self services developer, self service automation. Jeff- but this ticket is just to get information about a particular deployment correct? Ray - yeah this is the back end portion of the self service- This ticket is the console service tickets

Jeff- How does this align with our objectives? Dave - I think the answer is that it may or may not align with our objectives. If it does not align then one of two things needs to happen.

either we reopen this ticket and move it way down in the backlog because we are not going to touch it this year. Eventually we may decide this is not a thing we are going to do Jeff - may i propose that if we decide that it isn't aligned with any of our objectives we close this and make it disappear?

Dave - So i think the answer right now is that is a conversation where we would need to bring up to Chris and how this board is being used is also to show all of the work that is in our backlog that we can't get to because is not a priority to justify, give us more money.

annekerr49 commented 6 months ago

Aparna to follow up with Nate to see if this is out of date.

annekerr49 commented 6 months ago

Jennifer and Grace are touching base on this issue and I think they have worked a solution. I will keep you in the loop if additional help is needed. I think this is getting deprioritized due to Code.va.gov, Aparna will check with Nate to see if this is still relevant and if it is blocked or is not relevant any more.

EricaRobbins commented 4 weeks ago

@JeffKeeneVAGov - Either edit card or start new card for Code Owners.

department-of-veterans-affairs / va.gov-team