-
Notifications
You must be signed in to change notification settings - Fork 24
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
RFE: Separate keptn configure monitoring
from keptnInit
(Breaking change)
#80
Labels
breaking-change
type:feature
New feature or request that provides value to the stakeholders/end-users
Comments
christian-kreuzberger-dtx
added
type:feature
New feature or request that provides value to the stakeholders/end-users
breaking-change
labels
Jan 24, 2022
I set my pipeline to use this release,
I changed my pipeline to use the new function, However, I get this error in the Jenkins console.
|
@pcjeffmac I am moving your issue to #96 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
breaking-change
type:feature
New feature or request that provides value to the stakeholders/end-users
Problem statement.
As a user I would like to create a project, add some files (slo, sli, additional configuration), and then configure monitoring afterwards.
E.g.:
Current functionality
At the moment this functionaltiy is hidden within the
keptnInit
function, e.g.:However, depending on the monitoring solution this might fail, because additional files are required (dynatrace.conf, sli.yaml, slo.yaml).
Definition of Done
keptnConfigureMonitoring
implemented and documented in READMEkeptnInit
parametermonitoring
removed (BREAKING CHANGE)The text was updated successfully, but these errors were encountered: