Improve label-related warnings #89
Comments
|
Those messages come from the gcloud cli tool!
Given that the warnings are likely to show when the script is testing for
the **absence** of existing resources, I'm sure they could be safely
suppressed in these few instances.
…On Sun, 26 Feb 2023, 3:56 am hab25, ***@***.***> wrote:
When running setup.sh and scale-up.sh before having run scale-down.sh,
one gets the below warning multiple times at different points in time of
execution of these scripts. These warnings stop after running
scale-down.sh (given that one hasn't run destroy.sh).
WARNING: The following filter keys were not present in any resource : labels.gcloudrig, labels.latest
Warnings are particularly scary in this project because of the risk of
high cloud costs.
I suggest adding something like "If you haven't run
gcloudrig/scale-down.sh yet, this is expected." to the warning message.
—
Reply to this email directly, view it on GitHub
<#89>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AF5YVP4PHAP2UM4K2BYCSP3WZJBWVANCNFSM6AAAAAAVH7JYAA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
Suppressed by gcloudrig (not the user), right? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When running
setup.shandscale-up.shbefore having runscale-down.sh, one gets the below warning multiple times at different points in time of execution of these scripts. These warnings stop after runningscale-down.sh(given that one hasn't rundestroy.sh).Warnings are particularly scary in this project because of the risk of high cloud costs.
I suggest adding something like "If you haven't run
gcloudrig/scale-down.shyet, this is expected." to the warning message.The text was updated successfully, but these errors were encountered: