We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
v2 is more strict about workflow names than v1.
When migrating v1 projects with CLI deploy, we should be able to run a safe slugify function to strip out disallowed characters.
I expect this to be almost a one liner.
I guess the only question is if this creates any kind of sync problem. Do we only convert on first deploy or do we do it always?
The text was updated successfully, but these errors were encountered:
These real workflow names and step names cause problems:
Workflow-[BNS-1B]-1.Get-FormsList-(Historical-sync): name: Workflow [BNS-1B] 1.Get FormsList (Historical sync) jobs: [BNS-1B]-1.Get-FormsList-(Historical-sync): name: [BNS-1B] 1.Get FormsList (Historical sync) adaptor: '@openfn/[email protected]' body:
Sorry, something went wrong.
josephjclark
No branches or pull requests
v2 is more strict about workflow names than v1.
When migrating v1 projects with CLI deploy, we should be able to run a safe slugify function to strip out disallowed characters.
I expect this to be almost a one liner.
I guess the only question is if this creates any kind of sync problem. Do we only convert on first deploy or do we do it always?
The text was updated successfully, but these errors were encountered: