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

Decide how to manage simp-core in puppetsyncs #882

Open
op-ct opened this issue Apr 24, 2023 · 0 comments
Open

Decide how to manage simp-core in puppetsyncs #882

op-ct opened this issue Apr 24, 2023 · 0 comments
Labels

Comments

@op-ct
Copy link
Member

op-ct commented Apr 24, 2023

Currently, if simp-core is included in a puppetsync repolist, it is treated as a pupmod, which is probably the least significant aspect of its purpose. As a result, syncs will add a number of pupmod-specific file that are not be appropriate for simp-core's larger purpose (as seen in #875).

We need to decide how and what to handle for simp-core during puppetsyncs. It is reasonable to sync some assets (like LICENSE), but others will necessarily remain unique.

@op-ct op-ct added the bug label Apr 24, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
Status: Todo
Development

No branches or pull requests

1 participant