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

feat: Support multiple destinations for a healthcheck #2704

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

sbylica-splunk
Copy link
Contributor

No description provided.

@sbylica-splunk sbylica-splunk force-pushed the support_multiple_destinations_healthcheck branch from 8e6388b to e2272c6 Compare February 17, 2025 12:29
@@ -62,7 +62,7 @@ jobs:
with:
semantic_version: 18
extra_plugins: |
@semantic-release/exec
@semantic-release/exec@v6.0.3
Copy link
Contributor Author

Choose a reason for hiding this comment

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

This is fixed in: #2690 , but we need it for workflow to work properly

if re.search(regex, var_key):
found_destinations.append(var_variable)
return set(found_destinations)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

This could be imported from:

regex = r"^SC4S_DEST_SPLUNK_HEC_(.*)_URL$"

But a dot in "conf.d" is causing an import issue. Something to think about later I guess

@sbylica-splunk sbylica-splunk changed the title (WiP) feat: Support multiple destinations for a healthcheck feat: Support multiple destinations for a healthcheck Feb 17, 2025
@@ -14,11 +15,20 @@ def str_to_bool(value):
'yes'
}

def get_list_of_destinations():
Copy link
Contributor

@ikheifets-splunk ikheifets-splunk Feb 20, 2025

Choose a reason for hiding this comment

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

I just have 2 questions:

  • Are we planning to backport same logic from health check api to healthcheck
  • Are we planning to add same logic on entry point during startup (where we checking that default destination is healthy, probably we also need to check not only default)

P.S. It's just a questions, it doesn't mean that we need to do asap, we will just discuss it

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

Successfully merging this pull request may close these issues.

2 participants