The currently displayed deployment history is designed and tuned for app deployments both graphically and technically. The feature must be updated to accommodate decommissioning as well. This might mean creating a completely new feature to replace the existing one.
The new version of "Deployments" must be a more generic audit log that can hold both deployments and decommissions. A new model should seek to be backwards compatible so that existing documents can be kept/migrated.
It should be taken care to avoid misunderstanding around what an decommissioning actually is; the complete removal of an app from the environment.
Screenshots
Current:
New:
To be updated by design issue #6079
Considerations
There is a separate issue with the goal of changing persistence layer from CosmosDB to PostgreSQL #5492. Could this issue perform some of that work or vice versa?
Migration of existing documents to a new collection.
Support for other events? Rollback?
Acceptance criteria
A new app audit log for deployments and decommissioning events.
Specification tasks
[ ] Development tasks are defined
Development tasks
Add tasks here
Test
Add test cases here as checkboxes that are being tested as part of the changes.
Definition of done
Verify that this issue meets DoD (Only for project members) before closing.
[ ] Documentation is updated (if relevant)
[ ] Technical documentation (docs.altinn.studio)
[ ] User documentation (altinn.github.io/docs)
[ ] QA
[ ] Manual test is complete (if relevant)
[ ] Automated test is implemented (if relevant)
[ ] All tasks in this userstory are closed (i.e. remaining tasks are moved to other user stories or marked obsolete)
Description
The currently displayed deployment history is designed and tuned for app deployments both graphically and technically. The feature must be updated to accommodate decommissioning as well. This might mean creating a completely new feature to replace the existing one.
The new version of "Deployments" must be a more generic audit log that can hold both deployments and decommissions. A new model should seek to be backwards compatible so that existing documents can be kept/migrated.
It should be taken care to avoid misunderstanding around what an decommissioning actually is; the complete removal of an app from the environment.
Screenshots
Current:
New: To be updated by design issue #6079
Considerations
Acceptance criteria
Specification tasks
Development tasks
Test
Definition of done
Verify that this issue meets DoD (Only for project members) before closing.