Skip to content

Tracking On-going Enhancements #8

@cksapp

Description

@cksapp

Tracking ongoing enhancements to the project

To-Do

  • [ ] Possibly remove array input functions to better match API and keep consistency for -Id parameter (no need for parallel support)
  • Verbose output for /actions endpoint should check for verbose before making API call so we don't waste extra API calls when just making just actions
    a821726
  • Get DBPool Containers filters API response based on container names and default database, supports array of strings
    cdfda03
  • GitHub Actions
    • PSScriptAnalyzer for PS code scanning
    • PlatyPS for automatic markdown docs from PS help
    • ModuleBuilder for templating and compiling functions to psm1 file for publishing
    • Publish to PS gallery with user API key using GH secrets or equivalent secrets management
  • [ ] PS Classes for DBPool responses such as Containers, Parents, Node, User, etc.
    (Classes can be implemented by module user, main module development should K.I.S.S. and simply be wrapper for API. As if there are changes in response we can still output pertinent information without needlessly affecting module)
  • Strongly Type response output from API (Note to self: Put more detailed info, no idea what this was in regards to for API output, perhaps for above referenced PS Classes?)
  • Allow for Get-DBPoolContainers with -Status parameter to also work with -Name & -DefaultDatabase sets

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions