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

Add problem URL to error message #2111

Merged
merged 3 commits into from
Feb 5, 2024
Merged

Add problem URL to error message #2111

merged 3 commits into from
Feb 5, 2024

Conversation

seanstory
Copy link
Member

@seanstory seanstory commented Feb 1, 2024

See https://elastic.slack.com/archives/C7LLL50CA/p1706800182262059?thread_ts=1705426484.605769&cid=C7LLL50CA

Users can get an error that tells them that the tenant name is wrong, but it's difficult to track down what is causing this issue. Adding the URL will let us go track down which item is associated with a different tennant.

Checklists

Pre-Review Checklist

  • this PR has a meaningful title
  • this PR has a thorough description
  • Added a label for each target release version (example: v7.13.2, v7.14.0, v8.0.0)

Copy link
Contributor

@timgrein timgrein left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice improvement!

@seanstory seanstory enabled auto-merge (squash) February 5, 2024 14:49
@seanstory seanstory merged commit 1dd68d3 into main Feb 5, 2024
2 checks passed
@seanstory seanstory deleted the seanstory-patch-5 branch February 5, 2024 19:30
Copy link

github-actions bot commented Feb 5, 2024

💔 Failed to create backport PR(s)

The backport operation could not be completed due to the following error:
There are no branches to backport to. Aborting.

The backport PRs will be merged automatically after passing CI.

To backport manually run:
backport --pr 2111 --autoMerge --autoMergeMethod squash

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants