-
Notifications
You must be signed in to change notification settings - Fork 4
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
v3.5.0 release #337
v3.5.0 release #337
Conversation
Co-authored-by: tom-reinders <tom-reinders@users.noreply.github.com>
Co-authored-by: tom-reinders <tom-reinders@users.noreply.github.com>
…ate_volume TD-592 - Fix duplicate volume and fix variable description
…advance_filtering Event grid advanced filtering
…caler TD-592 - Use the correct variable for the port
…aform auto-detects github)
Update version in getting started example and remove git prefix (terr…
…ne_to_kubernetes_cronjob TD-592 - Add variable timezone to kubernetes cron_job
TD-592 Update changelog
This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation. |
Changed
Added
azure/event_grid_topic_subscription
: Add variableadvanced_filter
(Event grid advanced filtering #331) (71e1a5a)kubernetes/cron_job
: Add variabletimezone
(TD-592 - Add variable timezone to kubernetes cron_job #335) (dcd4faa)Fixed
kubernetes/deployment_with_service
: Fix duplicate volume (TD-592 - Fix duplicate volume and fix variable description #332) (da21136)kubernetes/cron_job
: Fix variable description (TD-592 - Fix duplicate volume and fix variable description #332) (da21136)kubernetes/deployment_with_service
: Fix bug where the http-scaler used the wrong port (TD-592 - Use the correct variable for the port #333) (270e394)Changelog: