todo

Cheat Sheet

GIT git clone repourl git Docker docker ps to list all running docker containers. AKS kubectl get pods list all pods in current cluster kubectl -n default logs -f deployment/altinn-storage --all-containers=True - get logs for all components of the same deployment kubectl describe pod [pod name] describes current state and lists environment variables for a given pod kubectl delete pod [pod name] deletes a pod and a new pod of the same deployment will start »

General

TODO Git git add . git commit -m “” Revert local commit git reset --soft HEAD~1 Azure CLI az login --use-device-code Kubectl »

Altinn Studio - Deployment Architecture

NOTE: Outdated stuff alert! Needs to be updated. Runtime is no longer deployed as part of Studio. The diagram below show the different applications that is part this. Repository Gitea is used as Repository in Altinn Studio App Development solution. There is one instance of Gitea running in a docker container in the solution. It uses cloud service database and cloud file share for configuration and remote repos. »

App Parameters

The different parameters can be configured either in Altinn Studio UI or through modifying the configuration files in the application repository. Supported App Parameters party type requirements Not (yet) supported App parameters Valid to Valid from See all issues related to App-Parameters on Github. »

App.csproj

Summary This is a c# project file that is generated when a new app is created. This project file is placed in the root of the app folder. This project file helps in compiling the app. »

applicationmetadata.json

Overview applicationmetadata.json describes meta information of an application. This is automatically generated on creation of a new application. This is located at /App/config/applicationmetadata.json in the app repo. Format ‘applicationmetadata.json’ has the application information such as application id, version information, organisation that owns the application, workflow information, form and attachment information. Application Metadata Format Below is an example of application metadata json format { "id": "Brreg-testappmetaattachment", "versionId": "1.0", "applicationOwnerId": "Brreg", "createdDateTime": "2019-05-23T20:26:29. »

Authorization

The authorization component as based on XACML 3.0 and support both simple and complex policies defined for applications. The Policy Decision Point The Policy Retriavel Point identifes the correct policy for a request The context handler get all information needed to authorize the request. The authorization component consist of a Policy Decision Point (PDP), Policy Retriaval Point (PRP) and is integrated with other external Policy Information Points. Apps integrated with PDP to authorize access to applications. »

Build & Test Capabilities

Below list the capabilities with a short description and possible link to the different components providing that capability. Software Generation Capabilties Code & Config Writing Capability Most of our code is written manually. See development application components to get a overview over tools and application we use. Build & Integration Enablement Capabilities Software Compilation & Validation The project uses .Net, Java or Typescript compilers. Sofware Linking & Packaging The project has the capability to build packages. »

CalculationHandler.cs

Arbeidet med POC har føreløpig ikke konkludert angående bruk av denne filen. Vil jobbes videre med i MVP. Overordnet ‘CalculationHandler.cs’ er en C# klasse hvor tjenesteutvikler kan plassere forretningslogikk som gjør kalkuleringer. Format Standard C# kode som kan gjøre bortimot alt. Uavklart: Hvordan Tjenester 3.0 skal validere/verifisere denne logikken. Utvikling Under opprettelse av en tjeneste vil en tom CalculationHandler opprettes. Hypotese: Tjenesteutvikler editerer på denne filen via Altinn Studio eller Visual Studio Code »