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

Allow for plugins to enhance how credentials are stored #10

Closed
14 tasks done
JTonda opened this issue Oct 8, 2018 · 0 comments
Closed
14 tasks done

Allow for plugins to enhance how credentials are stored #10

JTonda opened this issue Oct 8, 2018 · 0 comments
Assignees
Milestone

Comments

@JTonda
Copy link

JTonda commented Oct 8, 2018

Allow plugins to influence how credentials are stored.
Credentials are stored in plain text by default.
Only one plugin that modifies this behavior can be installed at a time.
If credentials are stored securely and no secure credential management plugin is installed, inform the user.

Carried to sprint 2
3 points remaining

*Accept feature with PM

Tasks:

  • Design new PMF architecture
    Assigned: @AHumanFromCA && @gejohnston && @lyzla01
    Status: Completed
  • Load infrastructure plugins prior to the imperative overrides loader
    Assigned: @gejohnston
    Status: Completed
  • Modify the Plugin Management Facility to allow for plugins that don't add groups
    Assigned: @gejohnston
    Status: Completed
  • Defer logging of PMF messages until after the logger has been initialized
    Assigned: @lyzla01
    Status: Completed
  • Load credential manager into config object passed into the overrides loader.
    The order, since we have no config, should be the last plugin wins. This will allow the default to win if there are no plugins. Implement a field changeable config file.
    Assigned: @AHumanFromCA
    Status: Completed
  • Modify installer to write overrides to the settings.json file
    Assigned: @gejohnston
    Status: Discontinued
  • Update system test
    Assigned: @lyzla01
    Status: Completed
  • Create integration test scenarios for Imperative
    Assigned: @gejohnston
    Status: Completed
  • Create integration tests in Imperative
    Assigned: @gejohnston
    Status: Completed
  • Create infrastructure plugin example
    Assigned: @gejohnston
    Status: Completed
  • Create infrastructure plugin doc
    Assigned: @gejohnston
    Status: In Progress
  • Incorporate infrastructure plugin doc into official documentation
    Assigned:
    Status: Not Started
  • Publish new version of Imperative
    Assigned:
    Status: Not Started
  • Bump imperative version in Zowe CLI.
    Assigned: @gejohnston
    Status: In Progress
    Parent of Allow plugins to use the OverridesLoader imperative#21
@JTonda JTonda assigned gejohnston and ghost Oct 8, 2018
@JTonda JTonda added this to the CA - 18PI4S2 milestone Oct 8, 2018
@ghost ghost added review and removed in progress labels Oct 8, 2018
@JTonda JTonda closed this as completed Oct 8, 2018
@JTonda JTonda added Sprint 1 and removed review labels Oct 8, 2018
matthewpwilson pushed a commit to matthewpwilson/zowe-cli that referenced this issue Mar 15, 2019
Add in system test code for uss issue command
matthewpwilson pushed a commit to matthewpwilson/zowe-cli that referenced this issue Apr 3, 2019
Add in system test code for uss issue commandSigned-off-by: ChrisPark <ganggiyam@gmail.com>
@JTonda JTonda unassigned ghost Feb 27, 2020
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

2 participants