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

./batou secrets edit broken when creating new environments? #184

Closed
ctheune opened this issue Jun 8, 2021 · 2 comments · Fixed by #224
Closed

./batou secrets edit broken when creating new environments? #184

ctheune opened this issue Jun 8, 2021 · 2 comments · Fixed by #224
Assignees
Labels
Milestone

Comments

@ctheune
Copy link
Member

ctheune commented Jun 8, 2021

No description provided.

@ctheune ctheune added this to the batou 2.3 milestone Jun 8, 2021
@icemac icemac self-assigned this Jul 15, 2021
@icemac
Copy link
Contributor

icemac commented Jul 15, 2021

I cannot reproduce this problem, that's what I did:

  • copy examples/tutorial-secrets/environments/gocept.cfg to dev.cfg (does not seem to be necessary)
  • call env GNUPGHOME=......./src/batou/secrets/tests/fixture/gnupg ./batou secrets edit dev
    • This allows me to change and save secrets/dev.cfg.
    • It also can be edited again.

I found the following problems while poking around:

  • When I create a secrets file for a new environment and do not change anything before closing a file in secrets is created but it has a length of 0 Bytes. Trying to edit this file fails because it could not be decoded and I get a traceback.
  • Creating a secrets file for a new environment and leaving members blank prevents batou from encrypting the file so it asks me to edit, encrypt or quit. If I choose quit I also end up with a zero bytes long file in secrets

Do you mean these kinds of problems?

@icemac icemac assigned ctheune and unassigned icemac Jul 15, 2021
@icemac icemac added the gocept label Aug 31, 2021
@ctheune
Copy link
Member Author

ctheune commented Aug 31, 2021

Yeah, sorry, I can't remember in detail and thought it was something like the workflow that you tried and seems to be working.

Would be great if you fixed the smaller issues you noticed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants