Skip to content
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

Remove reference to old starting token format in docs #1873

Merged
merged 1 commit into from
Mar 29, 2016

Conversation

JordonPhillips
Copy link
Member

There is one last remaining bit of the old world left, the RDS docs mentioned in #1835. There is a pr up at boto/botocore#849 to fix the code bug there, but the doc here is a bit challenging.

RDS is using the Marker value 0 to indicate that it will start at the beginning of the logs. I'm not sure how I feel about transforming our docs to show --starting-token eyJNYXJrZXIiOiAiMCJ9 or showing --Marker 0 instead. We could also potentially make another flag (--start-at-beginning) to suit this scenario. What do you guys think?

cc @kyleknap @jamesls

@JordonPhillips JordonPhillips added pr:needs-review This PR needs a review from a Member. and removed pr:needs-review This PR needs a review from a Member. labels Mar 23, 2016
@jamesls
Copy link
Member

jamesls commented Mar 29, 2016

:shipit:. Regarding, RDS my preference is to keep it as is for now.

@JordonPhillips JordonPhillips merged commit fb37647 into aws:develop Mar 29, 2016
@JordonPhillips JordonPhillips deleted the update-token-docs branch March 29, 2016 19:55
@nrdlngr
Copy link

nrdlngr commented Mar 30, 2016

It looks like all of these examples have been converted to Unicode files in this PR; they have non-ascii dashes in them that break the HTML builds. The AWS CLI reference seems to be able to convert the characters properly, which is probably why it doesn't break the Travis CI build, but local HTML builds on Mac and Ubuntu are failing.

Is there a way we can block non-ascii files from being committed to the AWS CLI examples? Or add a test that at least checks that the files are ASCII and break the Travis CI build with an error if they are not?

@jamesls
Copy link
Member

jamesls commented Mar 30, 2016

Yeah, I'm going to add a test for this now to ensure this doesn't happen again.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
pr:needs-review This PR needs a review from a Member.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants