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

Document steps to decomission an application #365

Open
2 tasks
acn-sbuad opened this issue Jan 9, 2023 · 2 comments
Open
2 tasks

Document steps to decomission an application #365

acn-sbuad opened this issue Jan 9, 2023 · 2 comments
Labels
kind/chore Typical issues like patching and deployment. kind/documentation Improvements or additions to documentation status/draft Status: When you create an issue before you have enough info to properly describe the issue. status/pending-feedback Awaiting clarification/input from stakeholders etc.

Comments

@acn-sbuad
Copy link
Contributor

acn-sbuad commented Jan 9, 2023 •
edited
Loading

Description

A change from Altinn 2 to Altinn 3 is that more responsibility lies on the application owner.
For decomissioning of an application the required steps should be documented so the app owner can take these steps.

Some insights from internal discussions: https://altinndevops.slack.com/archives/C0378DYQ7B9/p1672990478507789

  • Update applicationmetadata with validTo.
  • Verify in policy that appowner can delete instances. Add rule if nessesary
  • Delete instances in progress (optional. Users that open instances in progress will get 404 error)
  • Request the deployment be taken down from the environment (currently not self service)

Additional Information

No response

Tasks

  • Document required steps
  • QA

Acceptance Criterias

No response
@acn-sbuad acn-sbuad added status/draft Status: When you create an issue before you have enough info to properly describe the issue. kind/chore Typical issues like patching and deployment. labels Jan 9, 2023
@annerisbakk annerisbakk added the kind/documentation Improvements or additions to documentation label Jan 30, 2024
@SandGrainOne
Copy link
Member

Not sure if this belongs in Team Core as such, but moving it to Storage for now.

@SandGrainOne SandGrainOne transferred this issue from Altinn/altinn-platform Apr 5, 2024
@SandGrainOne SandGrainOne self-assigned this May 7, 2024
@olebhansen
Copy link

@nkylstad @RonnyB71 : should the app lifecycle be owned by Apps/Studio?

@olebhansen olebhansen added the status/pending-feedback Awaiting clarification/input from stakeholders etc. label Jul 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/chore Typical issues like patching and deployment. kind/documentation Improvements or additions to documentation status/draft Status: When you create an issue before you have enough info to properly describe the issue. status/pending-feedback Awaiting clarification/input from stakeholders etc.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@olebhansen @SandGrainOne @acn-sbuad @annerisbakk