-
Notifications
You must be signed in to change notification settings - Fork 525
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
benchmark: Use static URL value for admin console URL for slack automation #14345
benchmark: Use static URL value for admin console URL for slack automation #14345
Conversation
This pull request does not have a backport label. Could you fix it @1pkg? 🙏
|
|
@@ -43,6 +43,6 @@ output "apm_server_ip" { | |||
} | |||
|
|||
output "admin_console_url" { | |||
value = var.run_standalone ? "" : module.ec_deployment[0].admin_console_url | |||
value = var.run_standalone ? "https://cloud.elastic.co/deployments" : module.ec_deployment[0].admin_console_url |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Shouldn't this be admin.found.no
? If you're running it yourself, then you'll be able to see the deployment in the "normal" (user console) UI. But if it's running in CI, then you won't.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think there is a big difference, since it only uses this URL when run against the Moxy when no ESS deployment exists.
…lack automation (#14345) (#14349) (cherry picked from commit 9292d4b) Co-authored-by: Kostiantyn Masliuk <[email protected]>
Motivation/summary
This is a small fix to make existing slack automation in benchmark workflow to work as expected with standalone benchmark mode.
Checklist
For functional changes, consider:
How to test these changes
Related issues