Skip to content

Update commandline yaml docs#7753

Merged
ahh-docker merged 1 commit intodocker:masterfrom
seemethere:update_yaml
Nov 30, 2018
Merged

Update commandline yaml docs#7753
ahh-docker merged 1 commit intodocker:masterfrom
seemethere:update_yaml

Conversation

@seemethere
Copy link
Contributor

@seemethere seemethere commented Nov 26, 2018

Proposed changes

Updates the commandline yaml docs to the latest HEAD of
https://github.com/docker/cli/releases/tag/v18.09.0

Steps to do:

  1. Checkout revision on docker/cli
git -C ~/go/src/github.com/docker/cli fetch --all && git -C ~/go/src/github.com/docker/cli checkout v18.09.0
  1. Generate yamldocs
make -C ~/go/src/github.com/docker/cli -f docker.Makefile yamldocs
  1. Copy yamldocs over to the _data/engine-cli directory
cp ~/go/src/github.com/docker/cli/docs/yaml/gen/*.yaml _data/engine-cli/

This could be automated to be done on any release, or else we could make this a separate thing that can be updated automatically out of band from docker.github.io

@ahh-docker We should also probably cut a branch for 18.09 and do this process for that as well.

Unreleased project version (optional)

Related issues (optional)

Relates to #7358

@ahh-docker ahh-docker self-requested a review November 26, 2018 20:29
@ahh-docker ahh-docker self-assigned this Nov 26, 2018
@GordonTheTurtle
Copy link

GordonTheTurtle commented Nov 26, 2018

Deploy preview for docsdocker ready!

Built with commit c5c166a

https://deploy-preview-7753--docsdocker.netlify.com

@ahh-docker
Copy link
Contributor

@seemethere The other thing we need to look at, is do we need to create a fork of the docker/cli repo? If so, we need to write down those instructions too. What do we need to do if we need to fix broken links?

what do we do to make sure this is merged into docs.docker.com?

@ahh-docker
Copy link
Contributor

@seemethere Also, how we do generate this for a specific release? the instructions aren't here on how to do that.

@seemethere
Copy link
Contributor Author

@ahh-docker No fork would need to be created, for different releases you would just checkout the tag (i.e. instead of git checkout master you'd do a git checkout <TAG>)

For a specific release this could be an automated pull request that gets triggered upon a successful release. Currently the release team doesn't have the bandwidth to be able to do that but we can put it on our issue tracker to get done most likely in Q1.

@thaJeztah
Copy link
Member

git -C ~/go/src/github.com/docker/cli fetch --all && git -C ~/go/src/github.com/docker/cli checkout master

I think this should be using the 18.09 branch, otherwise there's a chance we fetch documentation for the next (19.03) release, and pull in changes that are not yet released

@seemethere
Copy link
Contributor Author

Updated to only reflect changes in the v18.09.0 tag

short: Run a command in a running container
long: Run a command in a running container
usage: docker container exec [OPTIONS] CONTAINER COMMAND [ARG...]
usage: docker container exec [OPTIONS] CONTAINER COMMAND [ARG...] [flags]
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hm.. interesting that it's adding the [flags] here. That was fixed on the CLI usage output in docker/cli#1069, but looks like a change may be needed for the code that generates the YAML 🤔

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Opened a PR with a fix; docker/cli#1539

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So @thaJeztah would you say these yaml docs are good to merge without the fix for now? Would like to get a resolution on this ASAP.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Let me try getting them merged; if you can then regenerate from the 18.09 release branch (instead of the tag), then it should be fixed. DM'ing some people on Slack now 😅

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@seemethere docker/cli#1540 was merged, so if you can update using the 18.09 release branch, we should be good to go 🤗

Copy link
Contributor

@ahh-docker ahh-docker left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. We need to move the instructions somewhere other than the PR. I'm going to copy them to docs-private/wiki.

Copy link
Member

@thaJeztah thaJeztah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

can you update from the 18.09 branch, now that the fix was merged? #7753 (comment)

@ahh-docker
Copy link
Contributor

@seemethere I tried to do this myself, and ran into some issues:

Fetching origin
Note: checking out 'v18.09.0'.

You are in 'detached HEAD' state. You can look around, make experimental
changes and commit them, and you can discard any commits you make in this
state without impacting any branches by performing another checkout.

If you want to create a new branch to retain commits you create, you may
do so (now or later) by using -b with the checkout command again. Example:

  git checkout -b <new-branch-name>

HEAD is now at 51668a30 Merge pull request #1483 from thaJeztah/18.09_backport_docs_fixes

$home/repos- make -C cli fetch -f docker.Makefile yamldocs
make: *** No rule to make target `fetch'.  Stop.

@seemethere
Copy link
Contributor Author

@ahh-docker Have updated the original OP with instructions without error. There was a leftover fetch argument from my copy/paste

Updates the commandline yaml docs to the latest HEAD of
`docker/cli@2d692aedb`

Signed-off-by: Eli Uriegas <eli.uriegas@docker.com>
@seemethere
Copy link
Contributor Author

Copy link
Member

@thaJeztah thaJeztah left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks!

@ahh-docker
Copy link
Contributor

@seemethere ready to merge? If so, I'll go ahead and merge it. LGTM.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants