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

Use CfgORBAT class property to determine formation deployment payload #14

Open
jmlane opened this issue Oct 24, 2018 · 1 comment · May be fixed by #15
Open

Use CfgORBAT class property to determine formation deployment payload #14

jmlane opened this issue Oct 24, 2018 · 1 comment · May be fixed by #15
Assignees

Comments

@jmlane
Copy link
Owner

jmlane commented Oct 24, 2018

Instead of hardcoded composition files per formation size, let's parse the CfgORBAT for a deployment property to determine how to deploy the formation at runtime.

@jmlane jmlane self-assigned this Oct 24, 2018
@jmlane jmlane linked a pull request Oct 31, 2018 that will close this issue
4 tasks
@jmlane
Copy link
Owner Author

jmlane commented Oct 31, 2018

I think going with a string that compiles to code is probably the most flexible. Adding additional properties later for default handling of different types of values can be added to the backlog.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant