Update pipeline #145

markdboyd · 2024-12-13T20:40:54Z

Changes proposed in this pull request:

Refactor pipeline to ensure that tenant-* and upload-dashboard-objects job always run on every new deploy
Re-enable smoke tests for production

For any logging statements, is there any chance that they could be logging sensitive data?
Are log statements using a logging library with a logging level set? Setting a logging level means that log statements "below" that level will not be written to the output. For example, if the logging level is set to INFO and debugging statements are written with log.debug or similar, then they won't be written to the otput, which can prevent unintentional leaks of sensitive data.

None, just ensuring that necessary jobs run in CI after every deploy

JasonTheMain

Looks good to me

markdboyd added 5 commits December 13, 2024 15:28

re-enable smoke tests in production

6139949

update triggers for prod jobs

1425eca

uncomment smoke-tests-production

91343e4

update job triggers

f3c49c2

reorganize file

99be901

markdboyd requested a review from a team as a code owner December 13, 2024 20:40

JasonTheMain approved these changes Dec 13, 2024

View reviewed changes

markdboyd merged commit e0f040a into main Dec 13, 2024
1 check passed

markdboyd deleted the update-pipeline branch December 13, 2024 20:43