bugraoz93 commented on code in PR #67012: URL: https://github.com/apache/airflow/pull/67012#discussion_r3430673394
########## chart/kustomize-overlays/kerberos/STATUS.yaml: ########## @@ -0,0 +1,47 @@ +# Licensed to the Apache Software Foundation (ASF) under one +# or more contributor license agreements. See the NOTICE file +# distributed with this work for additional information +# regarding copyright ownership. The ASF licenses this file +# to you under the Apache License, Version 2.0 (the +# "License"); you may not use this file except in compliance +# with the License. You may obtain a copy of the License at +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, +# software distributed under the License is distributed on an +# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY +# KIND, either express or implied. See the License for the +# specific language governing permissions and limitations +# under the License. + +# The verify: block below is the smoke-test contract consumed by +# `breeze k8s smoke-test-overlay kerberos`. Run that command locally +# with --promote-status to refresh chart-version + last-verified +# automatically after a successful run; CI re-runs the smoke test on +# every PR but never mutates this file (CI=true refuses +# --promote-status). +--- +status: tested +chart-version: 1.22.0 +last-verified: '2026-05-15' Review Comment: It is a moving target, but once the user runs it and confirms everything looks good, we should just commit it. This test can run in canary too if we decide we want that. Instead of keying off this date, we can follow up on something else for the badge, like job status from canary. I don't have a great answer for updating this in place in the repo without adding some amount of burden to the CI team. I can open a follow-up for implementing the badge though. We can improve this part within it. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
