-
Notifications
You must be signed in to change notification settings - Fork 7
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
LAGOON_SERVICE and LAGOON_CONTAINER variables #305
Comments
You're requesting these variables be created yes, because they do not currently exist? What purpose would you have for these variables? How would you see them being used? I can see them being easy enough to add though, but I'm curious to understand what you would be using them for. |
Well, they'd be really handy for customising PS1 :-p |
The problem you might have would be locally those variables may not exist though unless you set them. So your PS1 would need to know what is provided by Lagoon, and what is provided by you. But I'm sure you can figure it out. I'll see when we may be able to get these into the templates. There is a bit of work already for the templates being adjusted that this would be relatively easy to slot into though. |
Oh, good point. But yes, I'm sure we can figure that one out. Thanks! |
It would be handy if the variables mentioned in the subject line were populated with the names of the service name and the container name.
The text was updated successfully, but these errors were encountered: