Skip to content

consistent default environment #16

@buhman

Description

@buhman

Based on #15, I think the:

__global__:variable null env thing used in hubble.keys.*_password doesn't make sense. Instead, the default environment name should probably be literally whatever the default_section is.

Also, maybe the hubble environment prefix makes sense (I'm not completely convinced), but it probably would be better to make that a prefix of the environment, not the variable name.

Could you explain the reason for the hubble environment prefix? Is that just to avoid collisions with other keyrings?


This is obviously a series of backwards-incompatible changes.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions