When none set, generate a random installation name #609
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good 👍
Codecov Report
@@ Coverage Diff @@
## master #609 +/- ##
=========================================
Coverage ? 71.54%
=========================================
Files ? 51
Lines ? 2611
Branches ? 0
=========================================
Hits ? 1868
Misses ? 500
Partials ? 243
Continue to review full report at Codecov.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
Is there a way to test this feature, or at least indirectly? 🤔 |
The description of the app/internal/commands/install.go Line 66 in e45cba1
|
6e36287
to
7f8e56c
Compare
@thaJeztah do you think this make sense or shall we better wait for an engine API to install apps and manage unique random name generation ? |
For uniformity with `docker run` user experience. Note a full implementation would required to get the engine manage random name unicity, like it does for containers. Signed-off-by: Nicolas De Loof <nicolas.deloof@gmail.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
- What I did
Generate a random installation name when none is set by user for uniformity with
docker run
user experience.- How I did it
Vendored dockerd namegenerator.
Clean implementation would require engine to prevent name conflicts, would make sense once we have an engine-side "deploy" implementation
- How to verify it
docker app install
without a name, thendocker app ls
- Description for the changelog
A random installation name is generated when none is passed to
docker app install
.- A picture of a cute animal (not mandatory but encouraged)