Update opslevel error message to include a link for assistance

[efasel]

Add a link to the error message pointing to the explanation in MS Teams

[efasel]

@springernature/ee-release-engineering

[simonjohansson]

There is already a link

[efasel]

Oh, you’re right. I didn’t see that as it came before the error message. Might be the same for other people. 🤔

Also: the linked page does not say anything about failing pipelines. In contrast your announcement today does concisely and to the point provide the information to understand why the pipeline is failing.

I was also following the same "Please see …" pattern as other error messages are using.

[simonjohansson]

I would like to have user feedback that the link is not clear before changing anything. What I posted today was just a TLDR, but to actually take any action that message does not contain the necessary information, so you would need to read a linked deeper source anyways.

The failing pipeline issue(oh I don't know why this is failing) we are seeing is transient and will be resolved within a day or two, capturing the audience that have failed to get the message from our already extensive communication :) At that point the error message will be as clear as "unable to find cf manifest"