You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Alternative deployments, besides having to provision the list of vantage points in the inventory in the “Local” directory, also need to adapt the vp_list.txt file on the collector with their list of vantage points manually. The vp_list.txt file could be generated from the inventory as well.
Would you consider a PR that would implement this?
The text was updated successfully, but these errors were encountered:
Alternative deployments differ from RSSAC047. Please ask your sponsors before working on this. If they say that adding features that are not in RSSAC047 is part of your contract, and that we can have a "do this as RSSAC047" configuration setting that is on by default, adding those features is just fine.
Sorry for not being clear. I didn't mean an alternative deployment, but just a deployment of the initial implementation in this repository that completely follows RSSAC047v2 guidelines outlined in section 3 of RSSAC047v2.
Also my usage of the word "feature" was probably wrong. The proposal was to help eliminate the hardcoded constants that are part of the deployment configuration and not of the implementation. Other than the vp_list.txt no deployment configuration is hardcoded in the implementation. Besides that, the list of vantage points is also in your ansible inventory, right?
Alternative deployments, besides having to provision the list of vantage points in the inventory in the “Local” directory, also need to adapt the
vp_list.txt
file on the collector with their list of vantage points manually. Thevp_list.txt
file could be generated from the inventory as well.Would you consider a PR that would implement this?
The text was updated successfully, but these errors were encountered: