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

Deprecate explicitly setting metricName for all scalers #1074

Merged
merged 2 commits into from
Feb 27, 2023
Merged

Deprecate explicitly setting metricName for all scalers #1074

merged 2 commits into from
Feb 27, 2023

Conversation

yardenshoham
Copy link
Contributor

In v2.12 this setting will be internalized and should not be set by users

Checklist

  • Commits are signed with Developer Certificate of Origin (DCO)

Docs part of kedacore/keda#4235
Relates to kedacore/keda#4220

In v2.12 this setting will be internalized and should not be set by users

Signed-off-by: Yarden Shoham <[email protected]>
@yardenshoham yardenshoham requested a review from a team as a code owner February 21, 2023 18:49
@netlify
Copy link

netlify bot commented Feb 21, 2023

Deploy Preview for keda ready!

Name Link
🔨 Latest commit 1b432cb
🔍 Latest deploy log https://app.netlify.com/sites/keda/deploys/63f612925d71ca0007284194
😎 Deploy Preview https://deploy-preview-1074--keda.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

@tomkerkhove
Copy link
Member

@JorTurFer @zroubalik Any thoughts on annotating previous version to create awareness on the deprecation?

Co-authored-by: Tom Kerkhove <[email protected]>
Signed-off-by: Yarden Shoham <[email protected]>
@JorTurFer
Copy link
Member

@JorTurFer @zroubalik Any thoughts on annotating previous version to create awareness on the deprecation?

IDK... I guess that adding the annotation only to the versions where it is deprecated is more consistent. I mean, we have introduced a warning in the code. Let's add the annotation only to versions where the message is logged but I don't have a strong opinion, if @zroubalik agrees with annotating other versions too, go ahead

@zroubalik
Copy link
Member

@JorTurFer @zroubalik Any thoughts on annotating previous version to create awareness on the deprecation?

IDK... I guess that adding the annotation only to the versions where it is deprecated is more consistent. I mean, we have introduced a warning in the code. Let's add the annotation only to versions where the message is logged but I don't have a strong opinion, if @zroubalik agrees with annotating other versions too, go ahead

+1 let's keep it simple

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.

4 participants