-
Notifications
You must be signed in to change notification settings - Fork 147
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
[question/daisy] Why no region parameter? #445
Comments
I like the idea of implying the default region from the default zone, we
may also want a top level Daisy default in the worklfow/flag too as I
believe I made zone optional. Technically you could just be working with
regional resources so demanding you specify zone doesn't make sense.
…On Wed, Jun 13, 2018, 7:25 PM Gustavo Serra Scalet ***@***.***> wrote:
@zmarano <https://github.com/zmarano> @adjackura
<https://github.com/adjackura>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#445 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AQWyS_W_kZf9wS-0xJ7O58DoU-ESPL5uks5t8cmCgaJpZM4UnNpz>
.
|
Working only with regional resources? I always instantiate a machine so I always needed to define a zone. I can implement this later, but for now, please check the first approach I implemented on #434 , specifically c9f1884#diff-7b1669af81e6327ae6d38b7c32b4003bR57 |
well, It's working thanks to #434. I'll soon make use of it again for managing subnetworks on daisy so I guess this task can be closed for now |
gaohannk
pushed a commit
to gaohannk/compute-image-tools
that referenced
this issue
May 20, 2021
Correct deploy canary target
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I'm implementing ForwardingRule step on daisy as requested on #437 (comment) but I see that daisy is not ready for using region as a parameter. In order to implement it I thought about:
region = zone[:-2]
)-region
to be passed by command line for supplying that information, otherwise a valid error likeno region provided in step or workflow
might occur.What's your opinion on this?
The text was updated successfully, but these errors were encountered: