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

synth.metadata file conflicts for apiary #137

Closed
chingor13 opened this issue Nov 16, 2018 · 0 comments · Fixed by #141
Closed

synth.metadata file conflicts for apiary #137

chingor13 opened this issue Nov 16, 2018 · 0 comments · Fixed by #141
Assignees
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. 🚨 This issue needs some love. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.

Comments

@chingor13
Copy link
Contributor

Synthtool is now creating a synth.metadata file next to the synth.py script. For apiary clients, we reuse the same synth.py for each of the n clients because new clients come in and generated automatically.

We should either skip metadata for these clients, or be able to provide a path to the metadata file.

@JustinBeckwith JustinBeckwith added the triage me I really want to be triaged. label Nov 17, 2018
@theacodes theacodes added type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns. priority: p2 Moderately-important priority. Fix may not be included in next release. labels Nov 20, 2018
@theacodes theacodes self-assigned this Nov 20, 2018
@JustinBeckwith JustinBeckwith removed the triage me I really want to be triaged. label Nov 20, 2018
@yoshi-automation yoshi-automation added the 🚨 This issue needs some love. label Apr 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
priority: p2 Moderately-important priority. Fix may not be included in next release. 🚨 This issue needs some love. type: bug Error or flaw in code with unintended results or allowing sub-optimal usage patterns.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants