You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Epic: Maintenance and Improvements For Release v3.X #293
With the next major release version v3.0.0 of the secureCodeBox we want to apply some improvements and maintenance in our Repository. This issue should list all Major (breaking) changes due to maintenance.
Renaming Hooks
Cascading Scans
The current image name for the cascading scans as well as the directory name where its helm
chart "declarative-subsequent-scans" is located is not quite precise and could be miss leading.
To resolve this we want to change the name for directory and docker images to cascading-scans
This change will also impact the name of the helm chart and is therefore breaking.
MS Teams Webhook
We plan to generalize this Hook to Notify other providers as well.
The name of this hook will have to change.
This change will also impact the name of the helm chart and is therefore breaking.
Also potentially breaking as this migrates out CRDs to the new version apiextensions.k8s.io/v1 (from apiextensions.k8s.io/v1beta1), see issue #399.
We should perform this change before the kubernetes 1.22 release which should happen around August 21, best if we can do our release a bit earlier to give people some time to update their scb operator before they update their kubernetes version.
We might be able to make some changes to make these changes so that it avoid most scenarios where this could cause problems, but would probably still be best to do it in a major release to be sure.
Activity
[-]Maintenance For Release v3[/-][+]Maintenance and Improvements For Release v3.X[/+]J12934 commentedon May 5, 2021
Also potentially breaking as this migrates out CRDs to the new version
apiextensions.k8s.io/v1(fromapiextensions.k8s.io/v1beta1), see issue #399.We should perform this change before the kubernetes 1.22 release which should happen around August 21, best if we can do our release a bit earlier to give people some time to update their scb operator before they update their kubernetes version.
We might be able to make some changes to make these changes so that it avoid most scenarios where this could cause problems, but would probably still be best to do it in a major release to be sure.
[-]Maintenance and Improvements For Release v3.X[/-][+]Epic: Maintenance and Improvements For Release v3.X[/+]