Skip to content

configuration management / monitoring #9

@pnispero

Description

@pnispero

configuration management / monitoring

This description is tentative, still thinking about what exactly were going to implement
For pushing to production, we want this global configuration list for everything. For IOC apps, it'd be similar to cram ls, but written out in a list. And this list will be used by ansible configuration management.
Expectation vs reality comparison for confirmation.
Essentially its a list of what I want deployed, and ansible can deploy that and check that its there.
And the end-goal is to get rid of write permissions on the production release directories to prevent any unchecked changes/fixes on prod, any new changes/fixes should be a new deployment not done manually.

But for dev, we still want user to specify in CLI.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions