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

Simplify deployment troubleshooting #12960

Open
Tracked by #11895
mlqn opened this issue Jun 13, 2024 · 0 comments
Open
Tracked by #11895

Simplify deployment troubleshooting #12960

mlqn opened this issue Jun 13, 2024 · 0 comments
Labels
area/app-deploy Area: Related to deploying apps from Altinn Studio to Altinn Apps. kind/feature-request Feature request that will be considered. status/ready-for-specification Status: Used for issues that are ready for functional decription og detailed design. status/triage

Comments

@mlqn
Copy link
Contributor

mlqn commented Jun 13, 2024

Description

When an application fails to deploy, most users click on the build log link to see the error. While the build log is useful for tracking the progress of the deployment, it does not actually contain the real error, which can be found in operational-{org}-{env}-law.

A simple solution could be to add a link to their operational-{org}-{env}-law with a pre-filled query.

UPDATE: A better approach would be to display the error directly in the error message as proposed by @martinothamar (see Altinn/app-template-dotnet#215 (comment) and https://digdir.slack.com/archives/C0760NPT2BE/p1733924050990099?thread_ts=1733917496.141789&cid=C0760NPT2BE)

failed_deployment
@mlqn mlqn added kind/feature-request Feature request that will be considered. area/app-deploy Area: Related to deploying apps from Altinn Studio to Altinn Apps. status/triage labels Jun 13, 2024
@mlqn mlqn changed the title Link to the error in Application Insights Link to operational-{org}-{env}-law Aug 27, 2024
@mlqn mlqn changed the title Link to operational-{org}-{env}-law Simplify deployment troubleshooting Dec 11, 2024
@mlqn mlqn added the status/ready-for-specification Status: Used for issues that are ready for functional decription og detailed design. label Dec 11, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/app-deploy Area: Related to deploying apps from Altinn Studio to Altinn Apps. kind/feature-request Feature request that will be considered. status/ready-for-specification Status: Used for issues that are ready for functional decription og detailed design. status/triage
Projects
Status: No status
Development

No branches or pull requests

1 participant