feat: bump spec to v0.1.0-rc.2 (schedule assignment id)#5
Merged
Conversation
Tracks platform release v0.1.0-rc.2. Schedule assignments are now addressable by their own id: set ID on an upsert to update a specific assignment in place, or omit it to create a new one (the same name can be scheduled multiple times). The returned id can be used to reschedule or delete that instance. Delete now also accepts an id to remove a single assignment instead of all by name. - spec/SOURCE.md pinned to v0.1.0-rc.2; spec/client.yaml re-vendored - regenerated gen/client.gen.go - added ID to the four scheduled request facade types; delete name is now optional (omitted when deleting by id) - conformance cases cover the new id round-trip
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Tracks platform release
v0.1.0-rc.2. The only spec change sincerc.1is the schedule assignment id feature.What changed
Schedule assignments are now addressable by their own
id:UpsertUserScheduled/UpsertOrganizationScheduled): setIDto update a specific assignment in place, or omit it to create a new one — the same name can now be scheduled multiple times. The id is returned inScheduledAccepted.DeleteUserScheduled/DeleteOrganizationScheduled): setIDto remove a single assignment; omit it to delete every assignment by name (unchanged).Nameis now optional (omitted when deleting by id).How
spec/SOURCE.mdpinned tov0.1.0-rc.2;spec/client.yamlre-vendored from the release asset (byte-identical to the published spec).gen/client.gen.go(oapi-codegen v2.7.0 viamake generate).IDto the four scheduled request facade types inmodels.go.conformance_test.gocovers the new id round-trip (facade ↔ generated).go build,go vet, andgo test ./...pass (integration tests env-gated, skipped).