Skip to content
This repository has been archived by the owner on Apr 17, 2023. It is now read-only.

Ensure pct install scaffolds into the correct folder structure #181

Closed
3 tasks done
michaeltlombardi opened this issue Aug 19, 2021 · 0 comments · Fixed by #197
Closed
3 tasks done

Ensure pct install scaffolds into the correct folder structure #181

michaeltlombardi opened this issue Aug 19, 2021 · 0 comments · Fixed by #197
Assignees
Labels
enhancement New feature or request

Comments

@michaeltlombardi
Copy link
Contributor

michaeltlombardi commented Aug 19, 2021

When installing a Puppet Content Template, the install command should parse the pct-config for that template and place the template into the following folder structure: author/id/version/..., where author, id, and version are pulled from the config file and the contents are placed in the version folder.

Acceptance Criteria

  • If the yaml does not include the author, id, and version keys, it errors
  • If the template would override an existing template with the combination of keys, it errors and suggests using --force to override
  • If the template would override an existing template with the combination of keys and the --force flag is specified, it overwrites the existing template files with a debug message
@da-ar da-ar self-assigned this Aug 25, 2021
@da-ar da-ar added the enhancement New feature or request label Aug 25, 2021
da-ar added a commit to da-ar/pdkgo that referenced this issue Aug 31, 2021
Prior to this commit, templates were installed to the templates directory under their id. This change sees that templates are installed to a namespaced path using the data contained in `pct-config.yml`

i.e. author/id/version
e.g. puppetlabs/puppet-module-base/1.0.0

This allows for users to customise a template and share under their own namespace. It also allows for the retention of different versions of an installed template.
da-ar added a commit to da-ar/pdkgo that referenced this issue Aug 31, 2021
Prior to this commit, templates were installed to the templates directory under their id. This change sees that templates are installed to a namespaced path using the data contained in `pct-config.yml`

i.e. author/id/version
e.g. puppetlabs/puppet-module-base/1.0.0

This allows for users to customise a template and share under their own namespace. It also allows for the retention of different versions of an installed template.
da-ar added a commit to da-ar/pdkgo that referenced this issue Aug 31, 2021
Prior to this commit, templates were installed to the templates directory under their id. This change sees that templates are installed to a namespaced path using the data contained in `pct-config.yml`
da-ar added a commit to da-ar/pdkgo that referenced this issue Sep 1, 2021
Prior to this commit, templates were installed to the templates directory under their id. This change sees that templates are installed to a namespaced path using the data contained in `pct-config.yml`
da-ar added a commit to da-ar/pdkgo that referenced this issue Sep 1, 2021
Prior to this commit, templates were installed to the templates directory under their id. This change sees that templates are installed to a namespaced path using the data contained in `pct-config.yml`
da-ar added a commit to da-ar/pdkgo that referenced this issue Sep 1, 2021
Prior to this commit, templates were installed to the templates directory under their id. This change sees that templates are installed to a namespaced path using the data contained in `pct-config.yml`
da-ar added a commit to da-ar/pdkgo that referenced this issue Sep 2, 2021
Prior to this commit, templates were installed to the templates directory under their id. This change sees that templates are installed to a namespaced path using the data contained in `pct-config.yml`
da-ar added a commit to da-ar/pdkgo that referenced this issue Sep 2, 2021
This flag enables a template that already existing in the templatepath to be overwritten.
da-ar added a commit to da-ar/pdkgo that referenced this issue Sep 2, 2021
This flag enables a template that already existing in the templatepath to be overwritten.
da-ar added a commit to da-ar/pdkgo that referenced this issue Sep 2, 2021
This flag enables a template that already existing in the templatepath to be overwritten.
da-ar added a commit to da-ar/pdkgo that referenced this issue Sep 2, 2021
This flag enables a template that already existing in the templatepath to be overwritten.
da-ar added a commit to da-ar/pdkgo that referenced this issue Sep 2, 2021
This flag enables a template that already existing in the templatepath to be overwritten.
da-ar added a commit to da-ar/pdkgo that referenced this issue Sep 3, 2021
This flag enables a template that already existing in the templatepath to be overwritten.
da-ar added a commit to da-ar/pdkgo that referenced this issue Sep 3, 2021
This flag enables a template that already existing in the templatepath to be overwritten.
da-ar added a commit to da-ar/pdkgo that referenced this issue Sep 3, 2021
This flag enables a template that already existing in the templatepath to be overwritten.
da-ar added a commit to da-ar/pdkgo that referenced this issue Sep 3, 2021
This flag enables a template that already existing in the templatepath to be overwritten.
da-ar added a commit to da-ar/pdkgo that referenced this issue Sep 3, 2021
This flag enables a template that already existing in the templatepath to be overwritten.
@sanfrancrisko sanfrancrisko self-assigned this Sep 7, 2021
@sanfrancrisko sanfrancrisko linked a pull request Sep 7, 2021 that will close this issue
michaeltlombardi added a commit that referenced this issue Sep 7, 2021
sanfrancrisko pushed a commit that referenced this issue Sep 8, 2021
…yout

(GH-182) Find templates in new install folder structure
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants