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

Targets management version 4 #91

Merged
merged 3 commits into from
May 30, 2023
Merged

Targets management version 4 #91

merged 3 commits into from
May 30, 2023

Conversation

jku
Copy link
Owner

@jku jku commented May 29, 2023

Redesign targets management once more:

  • Users still make target content changes (outside of the tool)
  • Let repository do the actual metadata changes during signing-event (the method is called status() but signing_event_update() might be better)
  • Repository also documents the target changes at high level in the signing event
  • Users sign normally: "playground-sign "

This makes the UX cleaner and does not complicate the repository too much.

The expected targets metadata change in e2e tests is because the PlaygroundRepository does not figure out version numbers as smartly as SignerRepository does, and ends up bumping versions more than needed: this could be fixed but it's not critical targets metadata.

This change means "playground-status" now makes commits and pushes them to signing event branch. This means the commands name is now not very descriptive. Changing it should not be disruptive but I did not want to grow this PR, so leaving that for later.

Redesign targets management once more:
* Users still make target content changes (outside of the tool)
* Let repository do the actual metadata changes during signing-event
  (the method is called status() but signing_event_update() might be
  better)
* Repository also documents the target changes at high level in the
  signing event
* Users sign normally: "playground-sign <EVENT>"

This makes the UX much more neat and does not complicate the repository
too much.

The expected targets metadata change in e2e tests is because the
PlaygroundRepository does not figure out version numbers as smartly as
SignerRepository does, and ends up bumping versions more than needed: this
could be fixed but it's not critical targets metadata.

This change means "playground-status" now makes commits and pushes them
to signing event branch. This means the commands name is now not very
descriptive. Changing it should not be disruptive but I did not want to
grow this PR, so leaving that for later.
@jku
Copy link
Owner Author

jku commented May 29, 2023

Fixes #88
Fixes #67

@kommendorkapten
Copy link
Collaborator

Overall looks good! Especially the transfer of _build_targets et. al. to PlaygroundRepository makes sense IMO.

@jku
Copy link
Owner Author

jku commented May 30, 2023

Especially the transfer of _build_targets et. al. to PlaygroundRepository makes sense IMO.

Agreed, playground-sign is now clearly defined and the resulting commits make a lot more sense when looking at the history.

Thanks, I'll merge this (with some added some linting fixes straight from running "black")

@jku jku merged commit b9b6e41 into main May 30, 2023
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

Successfully merging this pull request may close these issues.

2 participants