Skip to content

portability test: state to spec#1466

Draft
josephjclark wants to merge 7 commits into
deploy-v1-with-v2-specfrom
test-state-to-spec
Draft

portability test: state to spec#1466
josephjclark wants to merge 7 commits into
deploy-v1-with-v2-specfrom
test-state-to-spec

Conversation

@josephjclark

Copy link
Copy Markdown
Collaborator

Using claude to look at converting a Project to a v1 spec file.

This is actualy more involved than I thought. I thought it was just stripping the uuids but actually there are some different key names too.

Should I stick with this approach or should we have a serialize('spec', opts) function? Maybe it's not worth it?

Do we need a v2 spec serializer?

@github-project-automation github-project-automation Bot moved this to New Issues in Core Jun 28, 2026
@josephjclark

josephjclark commented Jun 28, 2026

Copy link
Copy Markdown
Collaborator Author

this does seem to work so maybe it's good enough 🤔

@josephjclark

Copy link
Copy Markdown
Collaborator Author

Issue: credentials are not converted

@josephjclark

Copy link
Copy Markdown
Collaborator Author

Think I've pushed a credentials fix. It's really ugly because of subtle differences between spec and state. Probably I should create a to-spec serializer but the differences aren't quite pronounced enough that I want to do it. Also this is hopefully not code that's going to be exercised very much, so it an afford to be ugly.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: New Issues

Development

Successfully merging this pull request may close these issues.

2 participants