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

The naming of Local Controllers must be consistent between LCs and SDX #128

Open
sdonovan1985 opened this issue Nov 26, 2019 · 0 comments
Open

Comments

@sdonovan1985
Copy link
Collaborator

Initial Rules not loading
Rules not propagating from the SDX Controller to the Local Controller

These were initially two issues, but, in the end, they have the same root cause. They are still separate issues (they occur in different areas of related functionality) This took about a week or effort to track down what the issue was. Several days were relearning and instrumenting the code (which required adding some capabilities that previously did not exist to connection objects).

The problem, in the end, was a mismatch between what the SDX Controller's name for an LC is, and what the LC's name for itself is. The workaround is easy: change the manifest file. I need to decide was the correct solution is for this, however. There must be consistency in naming, and the manifest file allows for a not-user-friendly name and a user-friendly name. The LC was using the former, while the SDX Controller was using the latter. The correct solution isn't immediately clear to me

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

No branches or pull requests

1 participant