Skip to content
This repository has been archived by the owner on Jul 30, 2020. It is now read-only.

init command #115

Closed
chouseknecht opened this issue Aug 8, 2018 · 2 comments
Closed

init command #115

chouseknecht opened this issue Aug 8, 2018 · 2 comments

Comments

@chouseknecht
Copy link
Contributor

chouseknecht commented Aug 8, 2018

Based on the Galaxy CLI Developer workflow discussion here: https://docs.google.com/document/d/1nx65quXCyYORNel72rRCovyQo_qO5fhHlqrnKyYNlYU/edit?usp=sharing

mazer init will do the following:

  • Create a new Collection in the content path
  • Utilize static layouts based on what’s provided in the codebase. No templating. No user overrides.
  • For a Collection, template a repository directory structure matching atestuseraccount/ansible-testing-content. (Note: use the example just for the subdirs, and ignore individual files).
  • Not support legacy roles

Examples

Create new collection:

mazer init collection --namespace mynamespace --collection-name mynewrepo

Create new role in existing collection:

mazer init role --namespace mynamespace --collection-name myexistingrepo --role-name myrolename
@chouseknecht chouseknecht added this to the 3.1 Sprint 2 milestone Aug 8, 2018
@chouseknecht chouseknecht added this to To do in Feature Development via automation Aug 8, 2018
@chouseknecht chouseknecht changed the title Mazer init command init command Aug 8, 2018
@chouseknecht
Copy link
Contributor Author

One thing the init collection command should include is a .gitignore file containing a line for the release directory that may be created by the build command. For more on the build command, see #116.

@chouseknecht
Copy link
Contributor Author

init was removed. It will become part of Molecule.

Feature Development automation moved this from To do to Done Nov 15, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Development

No branches or pull requests

2 participants