Add native Debricked fcli module
Opened this issue · 0 comments
MikeTheSnowman commented
This enhancement request is somewhat related to #468, but different in that this enhancement request is suggesting the idea of implementing a native fcli command module for debricked (eg: fcli debricked *
).
Pros:
- One less binary to manage and write scripts against.
- Makes the Debricked appear, to customers, to truely be a part of the Fortify product family.
- Debricked users would benifit from fcli's advanced data output capabilities and consistent calling conventions.
Cons:
- We'd potentially be making another tool with duplicate functionality when there's already something that exists that works.
Challenges:
- Getting the Debricked team to help and contribute to the continued development/maitenance of the Debricked module.
- We'd probably need to do a little reverse engineering and reivew of the existing Debricked CLI to see if it's doing anything special.
- The way that Debricked organizes data in the web UI is quite different to how Fortifty organizes things. This will effect the entity names and command names that we will need to create. Maybe we can get some opinions from the Debricked people on this?
- If the Debricked CLI does any kind of build integration, then we'd need to figure out how to get fcli to do that.
- The Debricked REST API has some functionality missing and consistency issues.
- The Debricked REST API needs a bearer token to be generated in order to endpoints.
- To complicate matters, you can create a bearer token using either a username/password credentials, or with an API Token.
- If you use an API token, then there are two different levels of permissions that you can grant to that token which will effect which API endpoints you're able to call.