Comment 1 for bug 1817684

Doesn't this lead to hard-to-debug issues where everyone has slightly
different text in their overlay? It seems to quickly lead to each
deployment being slightly different in hard to understand ways, vs having
concrete artifacts that are shared.

Given the power of what you can do in an overlay, having it interact as a
concrete artifact doesn't seem terrible.

curl -o http://example.com/overlay.txt && juju deploy
cs:bundle/canonical-kubernetes --overlay overlay.txt
is just about as terse, but leaves you with something you can introspect.

I wouldn't say we can't do this, I would just be cautious around guiding
people to useful mechanisms, so that they don't end up having a hard time
understanding what they've done.

On Tue, Feb 26, 2019 at 11:30 AM Kenneth Koski <email address hidden>
wrote:

> Public bug reported:
>
> I would like to deploy CDK to AWS with GPU support, and would also like
> to be able to do this without having to create a new bundle.yaml or
> overlay file. The rationale for this is that I would like to minimize
> the friction for people new to Juju when I host a workshop for Kubeflow
> Day at SCaLE 17x.
>
> Right now, Juju allows something that is close to what I'm looking for
> in the form of passing in an overlay file. However, this functionality
> is a little heavyweight for doing one or two small patches to the yaml.
> Would it be possible to support reading in the overlay file from stdin?
> A common convention that matches what I think new users would expect is
> to allow reading from stdin if a dash is passed in instead of the
> filename:
>
> echo "services: kubernetes-worker: constraints: instance-
> type=p2.xlarge root-disk=16G" | juju deploy cs:bundle/canonical-
> kubernetes --overlay -
>
> This would also compose well for fetching overlays remotely, for
> something like this:
>
> curl http://example.com/overlay.txt | juju deploy cs:bundle
> /canonical-kubernetes --overlay -
>
> ** Affects: juju
> Importance: Undecided
> Status: New
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1817684
>
> Title:
> [Feature Request] Juju should allow customizing bundle deploy
> constraints via CLI
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1817684/+subscriptions
>