joeabbey / diver Goto Github PK

Currently output is formatted with a collection of \t and spaces... it's not consistent. Moving to "text/tabwriter" should make this clearer.

• get/set
• list / ls
• create / delete

Need to make a decision on which is the correct usage.

@gitcoleman I was thinking that it might be simple enough to export an existing service spec to a Docker compose file, that way you won't need to re-write existing services.

Need a strategy around version handling. Because some of the features / APIs we're working with / exposing are not part of the official API we can't rely on API Version and sometimes have to track on UCP Version (HRM / Interlock is an example of this). Mind-dump:

• Track feature / endpoint mapping somewhere
• Ensure we track UCP version and API version in sessions
• Different client per version? (probably not as the API doesn't diverge that much)
• Different feature handling per version (probably easier to begin with but can get messy)
• Etc...

Need to investigate if this is possible, as all normal client bundle operations are just Docker/Service(swarm) related.

Missing CSV Export of:

• Teams
• Roles
• Grants
• Collections

(determine if pre-defined objects are ignored or migrated too)

Also issues around the UUIDs that are created as part of objects.

The endpoint is:

GET / PULL /enzi/v0/config/auth/ldap

Support dump filename returned by the ucp api under header Content-Disposition has a nice timestamp, and may soon even include the ucp instance id. Please create support dump file using this name.

Return service endpoints making it easy to access a service from the CLI.

Will perhaps have a dependancy on being able to query nodes.

To work out what has changed on a service, this feature would compare the spec{} and the previousSpec{} and repot the differences.

After downloading, please add the functionality to upload as well , the dB gets refreshed everyday,so it should download and upload as well .

It would be good to have a version check on some commands, for new features that have been introduced in newer versions.

• List Services
• list tasks of a service and theirs state

Currently, the majority of HTTP error codes are handled in the wrong places. Better to pass them back to the originally called function so that the correct error message can be reported,

Downloaded the pre-compiled v0.3 binary and when running ./diver I can see duplicative entries for ucp:

./diver
This tool uses the native APIs to "dive" into Docker EE

Usage:
  diver [command]

Available Commands:
  dtr         Docker Trusted Registry
  help        Help about any command
  store       Docker Store
  ucp         Universal Control Plane 
  ucp         Universal Control Plane             <---
  version     Version and Release information about the diver tool

Flags:
  -h, --help           help for diver
      --logLevel int   Set the logging level [0=panic, 3=warning, 5=debug] (default 4)

Use "diver [command] --help" for more information about a command.

asciinema link

Version: 0.3
Build: 09bdb07f0d66936e873a10d541d3d6d117d9958b

Used to restart a service and rebalance it across the nodes, the use case is if a node went missing or new nodes have been added to the cluster.

User should be able to download the CVE database via the store

Currently the build environment is not a set location, which can lead to a problematic and non-reproducible build.

Idea is to pin make release to a docker golang container.

Just so we can keep on top of this.

Create a simple web server that can be used to test web hooks/calls are being generated by DTR

He plan is to simplify the readme and move the majority of documentation to multiple markdown files in ./docs.

Detailed here:

#130

The code is already code to take a container and get it’s net info, and now the code to detach and then attach. This may alleviate some issues, thoughts @trapier

"Pre-built diver binaries are available on the releases page https://github.com/docker/joeabbey/releases"

referes to /docker/joeabbey/

Is there an ETA to moving to the docker repository I'd rather it not get stuck.

• List
• Create

Missing feature is to set the default collection for a user.

diver ucp auth collections setdefault --id <id of user> --collection <id of collection

What up Dan,

Please add some sort of code to display which environment the diver user is currently working on. Currently i have 5 UCP environments configured and i need to know where I'm working when i use this tool.

Thanks

Capability to interact with UCP managers/workers through the CLI. This might be needed for the Service improvements in #54

Hey Dan,

I'm trying to enable color but i get a flag error no matter where i put the flag.

diver ucp services get tasks --color --name loan
diver ucp services get tasks --name loan --color
diver ucp services get --color tasks --name loan

Error: unknown flag: --color

Thanks

Currently when pulling the bundle and one already exists, diver outputs a success message and doesn't overwrite the original bundle.

Functionality missing to:

• List
• Create
• Delete

Missing features:

• Create
• Delete

Additional functionality to view and examine more containers through the UCP API, also tidy output.

Hi Dan,

I'm not getting any info back from the health command.

12:19:25 wcolemanadmin @ wcolemanlp <> Diver0.3 <> ./diver ucp services get health ?
~/bin/DanDiver/Diver0.2
12:19:29 wcolemanadmin @ wcolemanlp <> Diver0.3 <> ./diver ucp services get health loan
~/bin/DanDiver/Diver0.2
12:19:38 wcolemanadmin @ wcolemanlp <> Diver0.3 <> ./diver ucp services get health

Please let me know if i'm using the correct syntax.

Thanks

Backup / restore can be fragile and sometimes the best way is to just destroy and recreate (either on the same or new infra). Great functionality would be dump out all users/orgs/grants/roles/config (basically everything non-workload related) in a format that can be injected back into a new cluster.

We may already have 90% of what's required here with the auth subcommand, just need a way of writing it out raw, possibly dealing with UUID relationships, and maybe some reformatting of requests.

Missing Features:

• List
• Create
• Delete