Pratik

Are there any workarounds? Trying to see if there's some hacky way of using aactivator from fish until/if this feature is implemented.

Need this yesterday

I think locking would still be useful; the workflow we have internally is: * Create a PR * work on it until its good; this requires plan to see if...

@majormoses I think we're already past the point of causing confusion: `atlantis plan` and `atlantis apply` already mirror `terraform plan` and `terraform apply`

Or are you saying that since the atlantis plan lock file is not a terraform thing it should not use the terraform-like syntax?

There is a somewhat easy way around this in Github at least. * enable the Github branch protection option: 'Restrict who can push to matching branches' to only the atlantis...

Since this depends on atlantis being configured as a Github app, it seems to require https://github.com/runatlantis/atlantis/issues/418

For invalid syntax, perhaps the library should indicate that and/or fail rather than continuing to parse the invalid data and generating invalid codeowners.

I haven't been able to find any examples either

@briancurtin what do you mean by a "fully featured client"?