[Feature Request] Support Dynamic Configuration.

[keidarcy]

Thank you very much!! This project is super useful for CircleCI users.

I'm wondering if is there a plan to support Dynamic Configuration(https://circleci.com/docs/dynamic-config/).

At this moment, it's just Cannot find declaration for step <step>, if I want to use something from other files 😄.

[BeFunes]

Thank you very much @keidarcy!

Dynamic config can be done in a bunch of different ways, and unfortunately it will probably be very complicated to support all possible approaches comprehensively.

That said, we do plan on supporting at least basic situations - for instance looking for declarations in different files, which sounds like your case. It won't be for another couple of months at least I believe, but we'll be happy to let you know once it's out, so you can let us know if that works for you or how you'd like us to improve on it!

[Barabazs]

Hi @BeFunes Do you have more news about this feature? I'm also very interested in cross-file declaration support.

[JulesFaucherre]

Hey, we do not plan on implementing this feature in the short term. There is some clashes with the FYAML and it's hard to decide on a good approach for this.

We'll try looking into it but it's most likely going to happen in several months.

[nicolaschambrier]

Hello 👋 very interested in this feature too, to be honest something as simple as a meta-comment like # cci-import ../../.circleci/shared-config.yml that the runtime would dynamically interpret as the content itself would be perfect

[Skoti]

Hi, I'm also using dynamic config and there are a lot of files located in different directories. It would be great to support this, however, I understand it may be complicated.

In the meantime would it be possible to add an option to disable the linter in the settings?

Anytime I enter a CCI yaml file in VSCode I have everything in red because there are tons of errors like: "version is required", "Cannot find a declaration for", "Parameter steps is not defined" etc.
And the file is unreadable. Right now the only option is to uninstall the extension, although I'd like to use its other features.