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

Pdk preview docs #223

Merged
merged 7 commits into from
Aug 7, 2017
Merged

Pdk preview docs #223

merged 7 commits into from
Aug 7, 2017

Conversation

jbondpdx
Copy link
Contributor

@jbondpdx jbondpdx commented Aug 4, 2017

These have a reworked structure that should be much better for what users actually want to do with PDK. See pdk.md for the overview / getting started.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 90.774% when pulling a2a1de3 on jbondpdx:pdk-preview-docs into 8dcf53c on puppetlabs:master.

docs/pdk.md Outdated
1. [Generate a module](./pdk_generating_modules.md) using the `pdk new module` command.
1. [Validate your module](./pdk_testing.md), to verify that it is well-formed.
1. [Unit test](./pdk_testing.md) your module, to verify that all dependencies and directories are present.
1. [Generate a class]](./pdk_generating_modules.md) for your module, using the `pdk new class` command.
Copy link
Contributor

Choose a reason for hiding this comment

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

Extra ] here, also should the link be to ./pdk_generating_modules.md#generate-a-new-class

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I added more specific links to all these.


1. From the command line, run the `pdk new module` command, specifying the name of the module: `pdk new module module_name`

Optionally, to skip the interview questions and generate the module with default values, use the ``skip-interview` flag when you generate the module: `pdk new module module_name --skip-interview`
Copy link
Contributor

Choose a reason for hiding this comment

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

Extra ` here.

7. Where others can learn more: If you have a website where users can learn more about your module, enter the URL.
8. Where others can report issues: If you have a public bug tracker for your module, enter the URL.

1. If the metadata that PDK displays is correct, confirm to generate the module. If it is incorrect, enter `n` to cancel and start over.
Copy link
Contributor

Choose a reason for hiding this comment

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

Should confirm to generate the module indicate hitting the Enter key or typing y and then Enter?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I was thinking about this, but it also says what to do right in the interface. That said, I can add it though, I think it seems OK with it too.

@jbondpdx
Copy link
Contributor Author

jbondpdx commented Aug 4, 2017

Updated with respect to @bmjen 's comments.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 90.774% when pulling 9e7233d on jbondpdx:pdk-preview-docs into 8dcf53c on puppetlabs:master.

Argument | Description | Values | Default
----------------|:---------------:|:------------------:|-------------------------
`--template-url=git_url` | Overrides the template to use for this module. | A valid Git URL. | No default.
`--license=spdx_identifier` | Specifies the license this module is written under. | See https://spdx.org/licenses/ for a list of open source licenses, or use `proprietary`. | Apache 2.0
Copy link
Contributor

Choose a reason for hiding this comment

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

Tiny nit but the default license value is Apache-2.0

Copy link
Contributor

Choose a reason for hiding this comment

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

Good point, that - is actually rather important when it comes to linting and parsing on the Forge right?

Copy link
Contributor

Choose a reason for hiding this comment

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

Yes, but the actual value in PDK seems correct.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah, legit, good catch @scotje

Copy link
Contributor

Choose a reason for hiding this comment

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

Might be worth clarifying that they should use the "identifier" from that SPDX link.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 90.774% when pulling 5cbd079 on jbondpdx:pdk-preview-docs into 8dcf53c on puppetlabs:master.

@coveralls
Copy link

Coverage Status

Coverage remained the same at 90.774% when pulling 7b07030 on jbondpdx:pdk-preview-docs into 8dcf53c on puppetlabs:master.

@bmjen bmjen merged commit 44929d8 into puppetlabs:master Aug 7, 2017
@chelnak chelnak added the maintenance Internal maintenance work that shouldn't appear in the changelog label Jan 16, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
maintenance Internal maintenance work that shouldn't appear in the changelog
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants