Peter Debelak

@pankajsharma1 This is technically possible, but very difficult. See possible solution at https://stackoverflow.com/a/56467981/3945932.

Looking into this, I _think_ the issue has to do with rule L003 treating indentation levels as integers when there are potentially in-between values. Here are two simple examples: ```...

Of note, the following doesn't have lint errors: ```sql {% if true -%} {% set something = 'something' %} {% else -%} {% set something = 'something else' %} {%...

Yeah, I agree that trimming leading whitespace _shouldn't_ make any difference here to rule L003 since either way the jinja block has no effect on the outputted sql and thus...

From what I can tell, the `parse` function raises on parsing errors regardless of the value of `ignore` while both `fix` and `lint` will ignore parsing errors with that config....

I tried this out on an m1 mac, and I get `mach-o file, but is an incompatible architecture (have 'x86_64', need 'arm64e')` with the package as installed via pip. When...

Jumping in here, I was surprised that this wasn't called out as a breaking change in the changelog. A `meltano.yml` file that used to work with `meltano install` gives this...

@alanmcruickshank For me, I added the following to my `meltano.yml` and am hoping it means I never have to think about enviroments again: ```yaml default_environment: none environments: - name: none...

This problem made it hard to realize that I was running into the problem from #6405 since running `meltano install` succeeded in our docker build but didn't actually successfully set...

Hashicorp provider change appears to be working as expected for me.