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 isPromAvailable utility function #3629

Merged
merged 2 commits into from
May 24, 2024
Merged

Conversation

busma13
Copy link
Contributor

@busma13 busma13 commented May 23, 2024

Adds the isPromAvailable function to job-components that checks if promMetrics exist on context and if the API has been initialized.

@busma13 busma13 force-pushed the add-isPromAvailable-function branch from 9c24eb6 to 72e323d Compare May 23, 2024 23:25
@busma13 busma13 requested review from godber and sotojn May 23, 2024 23:41
@busma13 busma13 marked this pull request as ready for review May 23, 2024 23:41
@godber godber merged commit 1ede326 into master May 24, 2024
40 checks passed
@godber godber deleted the add-isPromAvailable-function branch May 24, 2024 14:52
godber pushed a commit that referenced this pull request May 24, 2024
#3627)

This is a follow-up PR to #3629 which created a utility function to test
if promMetrics are available, allowing assets to be backward compatible
with teraslice before promMetrics were introduced (< 1.4.0). At the same
time we decided to just make `isPromAvailable()` checks everywhere
promMetrics was used, instead of using a proxy to catch calls to
undefined functions. See #3625 for more details.

This PR makes the following changes:
- Removes the `promMetricsAPI` Proxy from `terafoundation`
- Add checks using `isPromAvailable` before all calls to
`promMetricsAPI` functions.
- Update `promMetrics docs`.
- Bump teraslice from 1.7.1 to 1.7.2
- Bump job-components from 0.75.0 to 0.75.1
- Bump terafoundation from 0.64.0 to 0.64.1
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