You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 13, 2024. It is now read-only.
The import of existing valid circleCI config files should just work.
Workaround
Changing
add_ssh_keys
to
add_ssh_keys: {}
fixes the problem.
BUT, such things are quite annoying when one once to get started with the VCE. Especially if one triple checked that the current manually written config is valid via
> circleci config validate
Config file at .circleci/config.yml is valid.
# This configuration has been automatically generated by the CircleCI Config SDK.
# For more information, see https://github.com/CircleCI-Public/circleci-config-sdk-ts
# SDK Version: 0.9.0-alpha.16
# VCE Version: v0.10.5
# Modeled with the CircleCI visual config editor.
# For more information, see https://github.com/CircleCI-Public/visual-config-editor
Node.js version
No response
In which operating systems have you tested?
macOS
Windows
Linux
Other
No response
The text was updated successfully, but these errors were encountered:
This is actually a Config SDK Parser issue, and I've closed this in CircleCI-Public/circleci-config-parser-ts#14 (Project is currently internal, will get that updated)
Thanks for raising!
Is there an existing issue for this?
Current behavior
The regular
add_ssh_keys
is not accepted by the VCE.Minimum reproduction code
https://gist.github.com/mathaeus/972c9e4ee827077b1a24d64a0e043978
Steps to reproduce
Import config with
add_ssh_keys
Expected behavior
The import of existing valid circleCI config files should just work.
Workaround
Changing
to
fixes the problem.
BUT, such things are quite annoying when one once to get started with the VCE. Especially if one triple checked that the current manually written config is valid via
CircleCI Config SDK version
Whatever the online editor gave me:
Node.js version
No response
In which operating systems have you tested?
Other
No response
The text was updated successfully, but these errors were encountered: