`bosh create release` should take `private.yml` credentials as arguments about bosh-cli HOT 9 CLOSED

@DanielJonesEB what do you think about specifying path to private.yml via cli flag. then you could do --private <(something here). or do you think private.yml should remain in the repo and just work with -l flag to interpolate variables?

cc @vito

from bosh-cli.

Thanks for taking the time to consider this, @cppforlife.

There are only three supported blobstore types at present, is that correct? Atmos, S3 and Local? If so, I think the user experience would be nicest if there was the option to specify the relevant values purely by command line --blobstore-type s3 --access-key foo --secret-key bar, although I can see that leads to three branches of 'special case' code.

Failing that, the variable interpolation would be cool. I'm not familiar with the -l flag: is that something new?

from bosh-cli.

we are planning to add --private-conf flag that can be used with bash's standard pipe redirect:

$ bosh create-release --final --private-conf <(lpass ... or may be bosh build-manifest ... -l ...)

from bosh-cli.

@cppforlife is Atmos still supported in bosh cli V2?

from bosh-cli.

@bonzofenix s3 and local are the currently supported types:

cc @cppforlife

from bosh-cli.

Hi @DanielJonesEB!

I simply want to check with you if this issue is still relevant to you. If that's still the case, I will have a deeper discussion on it with the engineering team. Please let me know.

from bosh-cli.

Thanks for following up! It's not causing any acute pain at the moment.

from bosh-cli.

This issue was marked as Stale because it has been open for 21 days without any activity. If no activity takes place in the coming 7 days it will automatically be close. To prevent this from happening remove the Stale label or comment below.

from bosh-cli.

This issue was closed because it has been labeled Stale for 7 days without subsequent activity. Feel free to re-open this issue at any time by commenting below.

from bosh-cli.