feature: migrate deployment parameter page to Angular and update to version 17.1

[llorentelemmc]

@yvespp while adding user permissions to deployment-parameter and tags components in Angular, I noticed that permissions are defined as either old or new (AMW_business/src/main/java/ch/puzzle/itc/mobiliar/business/security/entity/Permission.java). Do you know the reason why some are defined as old and some as new, and is it okay that MANAGE_GLOBAL_TAGS and MANAGE_DEPLOYMENT_PARAMETER are old?

[StephGit]

Please rebase to resolve the conflicts and fix the test deployment-parameter.component.spec.ts

[yvespp]

@yvespp while adding user permissions to deployment-parameter and tags components in Angular, I noticed that permissions are defined as either old or new (AMW_business/src/main/java/ch/puzzle/itc/mobiliar/business/security/entity/Permission.java). Do you know the reason why some are defined as old and some as new, and is it okay that MANAGE_GLOBAL_TAGS and MANAGE_DEPLOYMENT_PARAMETER are old?

Yes that's ok. The name is a bit misleading, the old permissions are global and the new are per resource, env etc. It's more like permissions are from the old (global) or new (scoped) permission concept.

[yvespp]

When switch from JSF (e.g. Propert Types) directly to Tags and Deployment Parameter I can see the "Add key"/"Add tag" button, but if I switch from an Angular page to the two new pages it doesn't show the buttons...

Same for the delete buttons.

[yvespp]

When I try to add a duplicate tag, the error toast sometimes shows for a short time only (less than a second, sometime it just blinks). The only reliable way I found to reproduce this spamming the add button with the same tag.

[yvespp]

It looks good to me now, thanks!
The toast still has a strange behaviour. It looks like the timer on the component keeps running even if a new toast is show (replacing the old before it's time) and then the old timer closes the new toast. Timer:

liima/AMW_angular/io/src/app/shared/elements/toast/toast.component.ts

Line 45 in 7c4fa31

setTimeout(() => {

May the old timer has to be canceled or it should only hide the toast if it matches the toast.
Should we merge this and you have a look in a separate issue?

[StephGit]

We resolved the timeout issue with clearing the old one first.

A improvement for the future would be, to show multiple toast instead of only one. Should we create a story for a toastContainer-Component?

[yvespp]

A improvement for the future would be, to show multiple toast instead of only one. Should we create a story for a toastContainer-Component?

I created an new issue for it: #744
NG-Bootstrap already hase something like this, maybe that could be used?